Aperture
Aperture copied to clipboard
aaronpk
Docker Image
One for once Aperture is more stable.
But I'm lazy, so a docker image would be great and make it easier for others to self host.
I don't like running things in Docker so I won't be tackling this, but I'm open to accepting a PR if someone puts it together.
I'm running Aperture in a Docker container, but I didn't really follow best practices back when I set it up. Not interested in creating an image now, but want to help doing it in a more correct way once someone needs this.
@sebsel Would you mind sharing your Dockerfile at least as a starting point for others? I would be running Aperture already if it were containerized.
I'd love a docker container too. @sebsel care to share yours, even if it isn't following best practices? I'd like a starting point too.
Sorry @fivestones, this is years ago and I have not been using it for a while now. The server I used is gone, so I have no idea how it looked like. I should have indeed shared some of it, but then again: it wasn't a good setup.
That said: it's just a Laravel application, so I would say start there. But I suppose you need two containers: one for the web and one for the background worker. It does not seem to use the php artisan schedule:run command on Cron, but maybe @aaronpk has other commands on Cron?
Point being: I don't think you're looking at one Docker container here, for there are several processes needed.
Good luck!
Sorry for jumping in here like this, but, just FYI, here's my "solution": https://github.com/janboddez/aperture-docker-compose, which will kick off not two, but seven containers (for Aperture itself, Watchtower, two databases, Beanstalk, Redis, and Camo). Plus, it requires setting up virtual hosts for Watchtower, Aperture and Camo. (The Watchtower worker is kept going by a systemd service on the host OS. If you'd like to use Aperture with Redis queuing, too, you'll need something similar there. I'm running it like that, but it's not in the repo, yet.)
(That said, it works, and I can really easily nuke my setup and bring it up again. At the same time, I'm fairly convinced that a separate WordPress install + Yarns, with its "hacky" WP-Cron scheduling, is much simpler to self-host.)