I think I settled on using peridot and logging in before every request that requires auth.

@yogthos in selmer is there a way to do {% if forloop.counter = 0 or forloop.counter = 1 %}

looking at the code I would say no. Maybe I can call a clojure method? if says evaluates a condition so could that be clojure call?

@llsouder you could do it using a filter (selmer.filters/add-filter! :matching-counter #(some #{%} [0 1])) and then {% if forloop.counter|matching-counter %}hello{% endif %}

thanks. Where does the (selmer.filters/add-filter! :matching-counter #(some #{%} [0 1])) go? in the template or the clj file?

that looks like clojure but the #{%} looks like template stuff.

that would go in the clj file

the #{%} is just set notation

I’m trying to figure out how to deploy a Luminus web app to Linode. I’ve read the excellent docs (http://www.luminusweb.net/docs/deployment.md) I was wondering how I could automate deployments as much as possible. My first thought was setting up a docker container and deploying it with dokku (git push a la Heroku). I would love to hear some other thoughts as well. Thanks in advance!

docker definitely works, another option to look at is vagrant

if you’re only running a single app on the node, then it probably makes more sense

The idea is to add at least one more separate web app for another subdomain

if you have multiple apps, then dockerizing is probably the way to go

but depends on the complexity of the apps as well, if you need external dependencies like queues, databases, etc, then I find docker is nice

if you just have the apps, then you can probably front with nginx easily enough

jars are already pretty self contained

I currently have a single DB for both apps and some reliance on the file system. Queues might come in the picture later on.

I guess it depends on whether you need isolation or not

if you’re sharing resources, I think vagrant is better

docker is nice specifically for cases where each app has its own independent stack

I’m somewhat familiar with Docker, but Vagrant looks nice as well

ansible is another nice tool for provisioning https://www.ansible.com/

A simple deploy script with some ssh commands might still be a viable option as well once nginx is setup

yeah if your setup is simple, no need to overcomplicate 🙂

As you said, jars are nice

the thing that’s nice with vagrant is that it lets you script the whole system setup, so you can easily rebuild it later

Looks very interesting for local dev environments

nowadays I like to treat system config as code, put it in a script, check it in the repo 🙂

otherwise you always end up with situations where you forget how you configured it originally and start scratching your head 🙂

That’s the good old days 😉

Thanks for your insights. 🙂

no prob 🙂