planningalerts | Find out have

by openaustralia Ruby Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | planningalerts Summary

planningalerts is a Ruby library. planningalerts has no bugs, it has no vulnerabilities and it has low support. However planningalerts has a Non-SPDX License. You can download it from GitHub.

Find out and have your say about development applications in your area. This is the code for the web application side of things written using Ruby on Rails. If you're interested in contributing a scraper read our step-by-step guide to writing scrapers on our scraping platform, morph.io. PlanningAlerts is brought to you by the OpenAustralia Foundation. It was created by Matthew Landauer and Katherine Szuminska.

Support

Quality

Security

License

Reuse

Support

planningalerts has a low active ecosystem.

It has 84 star(s) with 50 fork(s). There are 18 watchers for this library.

It had no major release in the last 6 months.

There are 106 open issues and 1339 have been closed. On average issues are closed in 450 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of planningalerts is current.

Quality

planningalerts has no bugs reported.

Security

planningalerts has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

planningalerts has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

planningalerts releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed planningalerts and discovered the below as its top functions. This is intended to give you an instant insight into planningalerts implemented functionality, and help decide if they suit your requirements.

Initializes a list of Users API
Enables the forms of the site
Unsubscribe
Confirms the comment .
Updates the site settings .
Imports an application
Checks if the user is authorized
Add a search to search tag
Export all active contacts
Adds a search tag to the search search criteria

Get all kandi verified functions for this library.

planningalerts Key Features

No Key Features are available at this moment for planningalerts.

planningalerts Examples and Code Snippets

No Code Snippets are available at this moment for planningalerts.

Community Discussions

No Community Discussions are available at this moment for planningalerts.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install planningalerts

In the oaf/infrastructure repo update roles/internal/planningalerts/meta/main.yml to add the new ruby version before the current one. The last listed one is the default. We don't yet want to change the default
Install the new ruby on the server by running ansible-playbook site.yml -l planningalerts. Remember to set your python virtual environment if you're using that.
Deploy new version of the application with upgraded .ruby-version to staging by running bundle exec cap -S stage=test deploy
Login to each webserver in turn (as root user). Then, cd /srv/www/staging/current; gem install bundler:1.17.3
Login to each webserver in turn (as deploy user). Then cd /srv/www/staging/current; bundle install --gemfile Gemfile --path /srv/www/staging/shared/bundle --deployment --without development test. This step is necessary if you're upgrading a ruby major version. You might be able to skip it if not.
Edit roles/internal/planningalerts/templates/default to change the ruby version used by passenger for staging in staging to the new version
Run ansible again with ansible-playbook site.yml -l planningalerts
Check deployed staging is still working by going https://www.test.planningalerts.org.au
During this keep a close eye on disk space on the root partition as this might get close to full.
Deploy new version of the application with upgraded .ruby-version to production by running bundle exec cap -S stage=production deploy
Check deployed production is still working by going https://www.planningalerts.org.au
Login to each webserver in turn (as deploy user). Then cd /srv/www/production/current; bundle install --gemfile Gemfile --path /srv/www/production/shared/bundle --deployment --without development test. This step is necessary if you're upgrading a ruby major version. You might be able to skip it if not.
Edit roles/internal/planningalerts/templates/default to change the ruby version used by passenger for production in staging to the new version
Run ansible again with ansible-playbook site.yml -l planningalerts
Check deployed production is still working by going https://www.planningalerts.org.au

Support

Fork the project on GitHub.Make a topic branch from the master branch.Make your changes and write tests.Commit the changes without making changes to any files that aren't related to your enhancement or fix.Send a pull request against the master branch.

Find more information at: