1. 31 Mar, 2018 1 commit
  2. 06 Mar, 2018 1 commit
  3. 15 Nov, 2017 1 commit
    • Daniel Hunsaker's avatar
      [Nanobox] Apply Release Notes Changes (#5670) · 3e4b01b4
      Daniel Hunsaker authored
      Apparently I missed some things in earlier commits/releases that needed to be applied to the Nanobox setup. All minor things, nothing that breaks anything, but still best to get them in place.
      - Move cron jobs to their own component, so the Sidekiq component can be scaled up to multiple instances without causing issues with running the same cron job multiple times at once.
      - Update cron jobs to the latest requirements, removing extraneous ones
      - Add new variables to `.env.nanobox`
      - Update Nginx to use correct cache header directives
  4. 06 Jul, 2017 1 commit
    • Daniel Hunsaker's avatar
      [nanobox] Add Automated Backups (#4023) · 185b41be
      Daniel Hunsaker authored
      This PR adds automatic backups to Nanobox instances. The database, Redis, and user files are backed up every day at 03:00 (server time) to the data warehouse component which comes with every Nanobox app. Old backups are automatically cleared out, but the number of backups that are left untouched can be configured by setting the `BACKUP_COUNT` environment variable to any integer value greater than 0 (the default is 1).
      Also updated `.env.nanobox` to reflect the current `.env.production.sample`.
  5. 29 May, 2017 1 commit
    • Daniel Hunsaker's avatar
      [nanobox] Adjustments for Nanobox development (#3295) · 9ead3d1c
      Daniel Hunsaker authored
      Because Nanobox doesn't run data components in the same container as the code, there are a few tweaks that need to be made in the configuration to get WebPack to work properly in development mode.
      The same differences lead to needing to use `DATABASE_URL` by default in the `.env` file for Rails to work correctly.
      Limitations of our `.env` loader for Node.js mean the `.env` file needs to be compiled everywhere in order to work, so we compile it in development, now, too. Also, all the `.env.production` tweaks have been consolidated into a single command.
      Finally, since Nanobox actually creates the database when it sets up the database server, using the existence of the database alone to determine whether to migrate or setup is insufficient. So we add a condition to `rake db:migrate:setup` to check whether any migrations have run - if the database doesn't exist yet, `db:setup` will be called; if it does, but no migrations have been run, `db:migrate` and `db:seed` are called instead (the same basic idea as what `db:setup` does, but it skips `db:create`, which will only cause problems with an existing DB); otherwise, only `db:migrate` is called.
      None of these changes should affect development, and all are designed not to interfere with existing behaviors in other environments.
  6. 23 May, 2017 1 commit
    • Daniel Hunsaker's avatar
      Add Support for Nanobox (#1709) · 256e3adc
      Daniel Hunsaker authored
      * Nanobox Support
      - Added support for running Mastodon using Nanobox, both for local development, and for deployment to production
      - Dev mode tested and is working properly
      - Deployment is undergoing test as of this writing. If it works, this line will be amended to state success; if not, one or more subsequent commits will provide fixes.
      * [nanobox] Resolve Deploy Issues
      Everything seems to work except routing to the streaming API. Will investigate with the Nanobox staff and make fix commits if needed.
      Changes made:
      - Also need `NODE_ENV` in production
      - Node runs on `:4000`
      - Use `envsubst` to commit `.env.production` values, since `dotEnv` packages don't always support referencing other variables
      - Can't precompile assets after `transform` hook, but do this locally so it only has to be done once.
      - Rails won't create `production.log` on its own, so we do this ourselves.
      - Some `start` commands run from `/data/` for some reason, so use absolute paths in command arguments
      * [nanobox] Update Ruby version
      * [nanobox] Fix db.rake Ruby code style issues
      * [nanobox] Minor Fixes
      Some minor adjustments to improve functionality:
      - Fixed routing to `web.stream` instances
      - Adjust `.env.nanobox` to properly generate a default `SMTP_FROM_ADDRESS` via `envsubst`
      - Update Nginx configs to properly support the needed HTTP version and headers for proper functionality (the streaming API doesn't work without some of these settings in place)
      * [nanobox] Move usage info to docs repo
      * [nanobox] Updates for 1.2.x
      - Need to leave out `pkg-config` since Nanobox deploys without Ruby's headers - create a gem group to exclude the gem during Nanobox installs, but allow it to remain part of the default set otherwise
      - Update cron jobs to cover new/updated Rake tasks
      - Update `.env.nanobox` to include latest defaults and additions
      * [nanobox] Fix for nokogumbo, added in 1.3.x
      Apparently, nokogumbo (pulled in by sanitize, added with `OEmbed Support for PreviewCard` (#2337) - 88725d6c) tries to install before nokogiri, despite needing nokogiri available to build properly. Instruct it to use the same settings as nokogiri does when building nokogiri directly, instead of via bundler.
      * [nanobox] Set NODE_ENV during asset compile
      The switch to WebPack will rely on the local value of the NODE_ENV evar, so set it to production during asset compilation.
      * [nanobox] Rebase on master; update Nginx configs
      - `pkg-config` Gem no longer causes issues in Nanobox, so revert the Gemfile change which allowed excluding it
      - Update Nginx configuration files with latest recommendations from production documentation
      - Rebase on master to Get This Merged
      Everything should be golden!
  7. 22 May, 2017 1 commit
  8. 20 May, 2017 1 commit
    • Wonderfall's avatar
      Some Dockerfile improvements (#3182) · ae78d012
      Wonderfall authored
      - improve docker_entrypoint.sh
      - serve static files with puma by default
      - sort packages list
      - use virtual package for build deps
      - show how to assign UID/GID
  9. 19 May, 2017 1 commit
  10. 08 May, 2017 1 commit
  11. 05 May, 2017 1 commit
    • ThibG's avatar
      Add additional documentation and warnings to the WEB_DOMAIN setting. (#2386) · 4d22d03f
      ThibG authored
      * Add additional documentation and warnings to the WEB_DOMAIN setting.
      This feature is largely undocumented, and quite a number of users have
      shot them in the feet already despite the warning. Added a bit of documentation
      and expanded the warning until we have a mechanism for dealing with conflicting
      user URIs.
      * Change WEB_DOMAIN comments to point to the extensive online documentation
  12. 04 May, 2017 1 commit
  13. 03 May, 2017 1 commit
  14. 02 May, 2017 1 commit
  15. 19 Apr, 2017 2 commits
  16. 17 Apr, 2017 3 commits
  17. 15 Apr, 2017 3 commits
  18. 13 Apr, 2017 1 commit
    • James Moore's avatar
      smtp delivery type fix (#1556) · d9dc0fe8
      James Moore authored
      * delivery fix
      # Conflicts:
      #	config/environments/production.rb
      * added stub in .env file
      * reordered and added a comment
  19. 10 Apr, 2017 1 commit
    • Alexander Mankuta's avatar
      More SMTP customization (#1372) · 0dbbc16c
      Alexander Mankuta authored
      * Allow SMTP auth method customization
      * Add SMTP openssl_verify_mode option support
      Allows one use self-signed certs with their SMTP server.
      * Add SMTP enable_starttls_auto option support
  20. 09 Apr, 2017 1 commit
  21. 07 Apr, 2017 4 commits
  22. 04 Apr, 2017 1 commit
    • Pete Keen's avatar
      [#817] Add email whitelist · e9a6da6b
      Pete Keen authored
      This adds the ability to filter user signup with a whitelist
      instead of or in addition to a blacklist.
      Fixes #817
  23. 23 Mar, 2017 1 commit
    • leopku's avatar
      🔧 S3 protocol from ENV · c46843c6
      leopku authored
      add support for reading S3 protocol from ENV
      also add S3_HOSTNAME in .env.production.sample
  24. 03 Feb, 2017 1 commit
    • Eugen Rochko's avatar
      Make the streaming API also handle websockets (because trying to get the... · ccb8ac85
      Eugen Rochko authored
      Make the streaming API also handle websockets (because trying to get the browser EventSource interface to
      work flawlessly was a nightmare). WARNING: This commit makes the web UI connect to the streaming API instead
      of ActionCable like before. This means that if you are upgrading, you should set that up beforehand.
  25. 29 Jan, 2017 1 commit
  26. 29 Dec, 2016 1 commit
  27. 06 Dec, 2016 1 commit
  28. 29 Nov, 2016 1 commit
  29. 26 Nov, 2016 1 commit
  30. 25 Nov, 2016 1 commit
  31. 23 Nov, 2016 1 commit
  32. 15 Oct, 2016 1 commit