-
Notifications
You must be signed in to change notification settings - Fork 9
Staging deployment #298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Staging deployment #298
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
viewing coverage locally
Minus rails 7 upgrades for now
…to develop and not my feature branch This reverts commit 03871d3.
…eport' into feature/rails-6-containerisation
… feature/rails-6-containerisation
…isation #1 Feature/rails 6 containerisation
#2 Update to the scss to make themeing more robust
…tion-editor #3 Adds a wysiwyg editor to the description field for services
#4 Feature/add postgres client
…ogic fix syntax error
Update favicon
Small fix to the full width layout page erroring
…text-fix Feature/wysiwyg and rich text fix
use puma as webserver update gemfile.lock to use the correct bundler version add app.json file remove windows from gemfile for heroku to stop regenerating it each deploy!
enable in-dyno databases for tests Update database_cleaner version for tests allow in-dyno database urls Update babelconfig for test environment to compile assets include chrome buildpacks for heroku tests Update selenium-webdrivers, remove webdrivers gem update chrome binary settings fix for :options error add 'test' docker compose file and update chrome settings
Feature/heroku 20 updates
Feature/develop
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This MR brings together a lot of things!
Highlights are:
Containerisation, though the architecture does need to change from alpine to be more inline with our heroku deployments
Tests now run in heroku and github (not locally yet because of the above issue)
The favicon is now outpost's one
some utility classes on the page layouts
wysiwyg editor (this feature is still in beta!)
updates to the scss so that settings apply to the website
updates to enable heroku-20 deployment
added superadmin role, similar to drupals user1 to protect the settings page
Restrict access to site settings page to superadmins #270
Viewing code coverage locally #271
Fix docker image issues #286 (parts of)
Feature/develop #291
Feature/heroku 20 updates #297
Feature/wysiwyg and rich text fix #296
Update favicon #293
#3 Adds a wysiwyg editor to the description field for services #289
#2 Update to the scss to make themeing more robust #288
#1 Feature/rails 6 containerisation #287
deployment notes:
NODE_OPTIONS=--openssl-legacy-provideris required for compiling the assets for the time being. This is because of webpacker, I managed to update thebabel.config.jsto remove a lot of the plugins that are included in preset-env now but theres one module left using md4 hash that we just can't do without for now.heroku buildpacks:add heroku/nodejs -i 1 --app app-nameto ensure nodejs buildpack is added and added first