Opened 10 years ago

Closed 9 years ago

#1031 closed enhancement (invalid)

Automated install of mediagoblin via salt

Reported by: arthur.lutz Owned by:
Priority: major Milestone:
Component: programming Keywords:
Cc: arthur.lutz Parent Tickets:

Description

I find the mediagoblin installation/deployment really tedious (and I believe the documentation could be better), so I started automating the deployment of mediagoblin using saltstack http://www.saltstack.com/community/ (python based in case you're wondering).

Here is the work in progress : https://gist.github.com/arthurlutz/ab7e9b3486f690a17a89 (and you'll need templated supervisor.conf and nginx.conf which I can upload if anyone is interested).

Is this of interest to anyone here ? Should I make this more usable ? Contribute it to the project ? Make it into a salt formula http://docs.saltstack.com/en/latest/topics/development/conventions/formulas.html ?

Attachments (2)

nginx.conf (2.2 KB ) - added by arthur.lutz 10 years ago.
supervisor.conf (551 bytes ) - added by arthur.lutz 10 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 by Christopher Allan Webber, 10 years ago

Heya Arthur,

This is great! I'm actually trying to review ways to do more automated deployment of MediaGoblin. I've been strongly considering salt and ansible both.

I'll took a closer look at your work over the next week. I think it's not likely that we're going to see the docs recommend a specific devops type solution, but I'd like to have one handy and have some to recommend on the wiki... and I'm hoping by using such a system myself maybe I can help figure out how to make deploying a bit easier.

Feel free to ping me on IRC if you like, I'm paroneayea in #mediagoblin on irc.freenode.net.

by arthur.lutz, 10 years ago

Attachment: nginx.conf added

by arthur.lutz, 10 years ago

Attachment: supervisor.conf added

comment:2 by arthur.lutz, 10 years ago

Good news cwebber.

Pillars need to include something like :

mediagoblin:

domain: example.org
postgresql_password: changepassword
postgresql_port: 5432

After this gets working I'll probably contribute a Vagrant config file. Recent versions of vagrant include a salt deployer, so it's quite easy to point to a default debian image and say "run this salt recipe on the VM".

The end user experience should be :

  • install vagrant + virtualbox
  • git clone mediagoblin (or download zip)
  • cd mediagoblin
  • vagrant up
  • open browser on http://localhost:8080

comment:3 by arthur.lutz, 10 years ago

on a side note, how come I'm getting email notifications of the stuff I write, but not of your response (can't find a setting in preferences).

comment:4 by Christopher Allan Webber, 10 years ago

Cc: arthur.lutz added

You have to add yourself to Cc:.

The current behavior for email updates is very confusing. I'm not sure what to do to improve it. If better Trac settings can be found, I will be happy to add them.

comment:5 by Christopher Allan Webber, 10 years ago

Also, that sounds like a great workflow for testing an install.

I think the best solution would be to have some way to have a test group that you can test by executing recent changes in Vagrant, as well as a way to push to production.

BTW, I'm not so sure this should be a bug... could you maybe move this conversation to the mailing list, then close this bug?

comment:6 by ayleph, 9 years ago

Resolution: invalid
Status: newclosed

I'm going to take the liberty of closing this ticket, as it isn't an issue affecting the code, nor something that would likely be added to the code, and it hasn't been updated for 9 months. Besides, the linked configuration calls in gstreamer0.10 packages which are no longer used in Mediagoblin.

Note: See TracTickets for help on using tickets.