In the past it was always useful to have meta data within regards to the SHA and
build date/time. This adds in two new env vars that are written to disk as flat
files and then exported to environment variables when the container starts up.
This motivation comes from this comment:
https://github.com/forem/forem/pull/9987#discussion_r476123829
* Replace HEROKU_SLUG_COMMIT with custom footprint (naive)
* Fully set RELEASE_FOOTPRINT with the expectation of setting it before launch
* Change tests
* Fix cache
* Moves badge_achievement-related code from /admin/bagdes to /admin/badge_achievements
- Adds an Admin::BadgeAchievements::Controller
- Moves #award and #award_badges to Admin::BadgeAchievements::Controller
- Removes #award and #award_badges from Admin::Badges::Controller
- Moves award.html.erb from /admin/badges to /admin/badge_achievements
- Removes badge_achievement routes from /admin/badges
- Adds a redirect for /admin/badges/badge_achievements to routes.rb
- Cleans up and refactors code in controllers, views, and routes
* Add more actions to Admin::BadgeAchievements::Controller and matching routes
- Adds an #index and #destory action to the BadgeAchievements::Controller
- Adds destroy to the badge_achievements routes
- Adjusts redirects for badge_achievements in routes.rb
- Removes dead code from the index view for Badges
- Refactors the existing code in the index view for BadgeAchievements
* Adds an /admin/badge_achievements_spec and cleans up the /admin/badges_spec
- Removes the badge_achievement-related tests from badges_spec.rb
- Adds an additional test around deleting badge_achievements
* Add pagination to badge_achievements index view
* Adds badge_achievements to Admin menu items and add comment to routes.rb
-Add badge_achievements to the Admin nav bar
-Add a comment regarding redirects for badge_achievements
* Resolve JS console stacktrace notices and change wording on deletion buttons
* Add a Back to Badge Achievements button to the badge award form
* Adjust styling to fix failing /admin/badges_spec.rb
* Uses SQL paging to optimize scalibility and adds search functionality to index.html.erb
- Use SQL paging in Admin::BadgeAchievements::Controller in #index and #award
- Add a search by user ID to Badge Achievements index view
- Add a limit of 15 badges to be shown on the Badge Achievement index view
- Add a User ID column to the Badge Achievement index view
* Add Award Badge button back to Badge Achievement index.html.erb
* Change @badge to be more explicit and reword warning around badge deletion
* Adds award badge button back, rewords success message, and adjusts SQL paging
* feat: add a select and a new text field
* feat: groups need to be unique and present
* feat: make the ui a little better
* chore: update the label
* chore: just present
* feat: add some js ( still a work in progress)
* feat: update the interface to work better :)
* chore: indent
* feat: make sure the toggles work
* chore: rename more aptly
* refactor: toggling pulled out into two functions
* refactor: move group form to a partial so that we can reuse it
* chore: move the js to the group form
* chore: update alignment and nav element
* chore: update text
* chore: update specs
* Fixed save button, but it's slow to update when clicking unsave
* Update app/javascript/articles/components/SaveButton.jsx
Co-authored-by: Nick Taylor <nick@iamdeveloper.com>
* Update app/javascript/articles/components/SaveButton.jsx
Co-authored-by: Nick Taylor <nick@iamdeveloper.com>
* Update app/javascript/articles/components/SaveButton.jsx
Co-authored-by: Nick Taylor <nick@iamdeveloper.com>
* I added the suggested changes but the issue still persists
* Added tests.
Co-authored-by: Nick Taylor <nick@iamdeveloper.com>
Co-authored-by: Nick Taylor <nick@dev.to>
RELEASE_FOOTPRINT will be set to the output of date -u +'%Y-%m-%dT%H:%M:%SZ'
(2020-08-25T02:02:21Z for example) which will fix https://github.com/forem/forem/pull/9904
This will be reset to a new date and time string every time the container starts.
* Mess with ssl
* Add redirect false
* Remove redirect config
* Redirect back to false
* Mess with validrequest
* Add validrequest back in
* Secure sessions
* Add domain to session_store
* Fiddle with ssl options
* Fiddle with secure
* Same site lax
* Remove force_ssl
* Remove domain from session_store
* Add domain back
* Secure session cookie
* Set secure with var
* Revert default_url_options change
* Set session store to secure
* revert secure force
* Revert unintended change
* The cookie domain property should not be set on localhost
* Switch to no domain unless in production
Co-authored-by: rhymes <rhymes@hey.com>
