โจ It's live! My start to finish guide for getting your own #mastodon instance up and running with Docker on Ubuntu 16.04: https://github.com/ummjackson/mastodon-guide/blob/master/up-and-running.md
I've tested this on both Vultr and DigitalOcean and the instructions should be pretty much copy/paste for everyone. Hope this helps some people! ๐
Good luck and feedback appreciated!! (cc @Gargron / @TonyNof / @david / @vielmetti / @lmorchard )
@ummjackson @internaut @Gargron @TonyNof @vielmetti @lmorchard Going to check, woot! ๐๐พ
@ummjackson @lmorchard @vielmetti @david @TonyNof @Gargron Wow, I was literally just writing a toot asking for documentation on starting up an instance. Thanks!
@rogersherman @Gargron @TonyNof @david @vielmetti @lmorchard Happy to help! Spent most of today working on getting my own instance(s) setup. Let me know if you have any questions.
@ummjackson @Gargron @TonyNof @david @vielmetti @lmorchard
Just getting started on Mastodon
@ummjackson Anyway to do this on an amazon s3 server? I ask as that seems to be the most popular option for server hosting stuffs.
@ummjackson Nice one! I did similar but modified the compose so I can run it all under a docker swarm stack!
@ummjackson I've been doing pretty much the same stuff you describe on a scaleway VPS and it also works fine, I guess as long as it's similar to Ubuntu 16.04 these instructions should largely be univeral :)
put it on hub.docker.com!
@lmorchard @vielmetti @david @TonyNof @Gargron note: the mastodon user doesn't require root privileges... will edit the article in the future but it's a relatively minor tweak and if you know your way around you can figure out how to avoid that. :)
@ummjackson @gargron @david @vielmetti @lmorchard you rock!! Thanks for all your hard work - I'll test it out in a few hours
@ummjackson @lmorchard @vielmetti @TonyNof @Gargron the extra `server {` you mention at the end of the file isnโt needed. Other than that, perfect guide!
@david What makes you say it's not required? Did it cause an error for you?
@lmorchard @ummjackson I am on vultr
@ummjackson You might consider submitting that as a pull request to Mastodon itself!
@lmorchard @vielmetti @david @TonyNof @Gargron @ummjackson thanks for writing this! I work for DigitalOcean and can't wait to set up a shard. :)
@taotetek @Gargron @TonyNof @david @vielmetti @lmorchard Good luck with it! ๐
@ummjackson I'm hoping it'll still work on my setup - I run my own web server on one of my macs
@taotetek @lmorchard @vielmetti @david @gargron @ummjackson if you work for DigitalOcean, I think you should hook ummjackson up with a discount ๐๐ค
@TonyNof @taotetek @lmorchard @vielmetti @david @Gargron always up for credits ๐ค hehe
@ummjackson @david @gargron once I get it up and running - I gotta buy you a beer lol
@ummjackson @Gargron @david @vielmetti @lmorchard @TonyNof our community team has editors who work authors on articles for the community site, and I know they pay for articles. I could hit them up about your tutorial and have someone get in touch. :)
@ummjackson Thanks for doing this, Jackson!
@ummjackson this worked perfectly for me - i finally have my instance up and running. thanks for writing this up!
@wolfteeth yay, awesome!! ๐
@ummjackson wow, nice work! i'm bouncing around mastodonia to let people know that sparkpost is a great alternative for mailgun, similar setup but 100K free/month https://sparkpo.st/smtp (disclosure: i work there and i'm happy to help if anyone has questions)
Thanks for putting this guide together!
@ummjackson Thank you!
@ummjackson @lmorchard @vielmetti @david @TonyNof @Gargron I get an error when I try to restart nginx and have no idea what to do.
@jasongreen what's the error?
@ummjackson job failed because control process exited with error code
@jasongreen Hmm, can you try running "sudo service nginx stop" and then try restarting?
@jasongreen To try and nail down the issue, try these commands:
"sudo nginx -t"
"sudo tail /var/log/nginx/error.log"
See if that gives you any insight into what's wrong... my thinking is that your site config might contain an error.
@ummjackson unexpected EOF expected }
Found and fixed. Thanks for your help. nginx -t gave useful information
@jasongreen awesome! Glad you found a fix ๐๐
@ummjackson just left the final } off the config file.
@ummjackson What docker commands do you need to run to update your instance if you make changes to .env.production ?
@jasongreen just these two: docker-compose build and then docker-compose up -d
@ummjackson thanks. Tried to solve my mail problem by creating account on my regular domain but mastodon still won't send confirmation email.
@jasongreen Hmm that's odd... any SMTP sender should work. There are a few good providers out there, give Postmark a try if MailGun isn't working for you.
@ummjackson trying sparkpost at the moment but having different problems there. Thanks for your help.
@jasongreen no problem, let me know how it goes!
@ummjackson I cannot get my instance to send a confirmation email. Tried direct to account on my usual mail host, mailgun, and sparkpost .
@jasongreen go to mailgun and view the message by clicking the cog wheel next to it. copy paste the confirmation manually
@ummjackson The message never shows up in mailgun. I don't think it's getting to mailgun.
@jasongreen Hmm, you can manually confirm yourself with:
docker-compose run --rm web mastodon:confirm_email USER_EMAIL=alice@alice.com
@ummjackson get Error: cannot start service web: OLI runtime error: container_linux.go:247: starting container process caused "exec: \"mastodon:confirm_email\": executable file not found in $PATH
@jasongreen ahh I must have gotten the command wrong - try mastodon_web instead of web... out and about so can't look it up right now
@ummjackson no hurry. Thanks again for your assistance
mastodon_web gives no such service error
@lmorchard @vielmetti @david @TonyNof @Gargron + cc/ @internaut :)