Snappy

13 ms·

1. 61.▲
   by Snappy 10y ago

   First off, I'll admit our documentation for caching needs improvement. We do support caching of gem's and other file artifacts. There are tricks about file locations, but once you get the hang of it, it works well. See https:&#x2
2. 62.▲
   by Snappy 10y ago

   Great summary of GitLab CI's advantages. Nice, easy read. Thanks Pierre! (Disclaimer: I work at GitLab)
3. 63.▲
   by Snappy 10y ago

   Take a look at GitLab's plan for Issue Boards ( https://gitlab.com/gitlab-org/gitlab-ce/issues/17907 ). It's not quite Jira, more like Trello, but a great step in solving modern issue management and p
4. 64.▲
   by Snappy 10y ago

   Thanks! Glad you like the direction!
5. 65.▲
   by Snappy 10y ago

   Yes, it's a GitLab EE-only feature, but it's also available for free on GitLab.com, which is running GitLab EE.
6. 66.▲
   by Snappy 10y ago

   If you're going to use the shared runners, I don't think that configuration is going to work. The build step will build it locally, and even though you named it to use the registry, it won't actually push to the registry auto
7. 67.▲
   by Snappy 10y ago

   Thanks! No current plans for rkt, but feel free to create an issue to discuss it.
8. 68.▲
   by Snappy 10y ago

   It really comes down to cost and convenience. We don't charge anything additional to run the container registry (including unlimited private projects for personal or business use), and it's already installed with GitLab. Having sa
9. 69.▲
   by Snappy 10y ago

   Yeah, sorry about that. We'll update the blog post to clarify. We're updating the CI runners this week to support this.
10. 70.▲
    by Snappy 11y ago

    You can run a post deploy script to load development data. e.g. `rake db:seed`.
11. 71.▲
    by Snappy 14y ago

    Heroku scheduler runs in a separate dyno so that wouldn't impact idling of the web dyno.
12. 72.▲
    by Snappy 14y ago

    For (2), Type `aspen` in the search bar of Heroku Dashboard.
13. 73.▲
    by Snappy 14y ago

    Don't forget the continuous protection backups...
14. 74.▲
    by Snappy 14y ago

    But was it serving _your_ 500 error page? In which case you could make it say anything you want. Heroku platform errors are not 500s; they're 502s (or 503s, I forget).
15. 75.▲
    by Snappy 14y ago

    You mean like this? https://devcenter.heroku.com/articles/error-pages#customize_...
16. 76.▲
    by Snappy 14y ago

    Thanks for the feedback. We (Heroku) have been wondering if people would prefer that.