zonque / alride

Very simple ride sharing tool, implemented with Ruby on Rails

AlRide - simple ride sharing platform

AlRide is a ride sharing platform that is as simple as is gets.

Anyone may enter ride offers and ride requests, and other people are able to contact the submitter through a contact form. The email address is not shown to anyone on the website, but only stored internally. The main view will only show database entries that are in the future (minus some slack).

Each entry has a random secret assigned that is attached to a removal link which is added to every mail that is sent to an entry submitter. This way, no user management, authentication logic, role management or anything is needed.

Built with Rails, Bootstrap and HAML.

Installing

Self-hosting

AlRide is a standard Rails 7 application. You can pretty much follow any of the available install guides, or follow the one below.

Basically, to get started you need git, ruby (>= 3.0) and the bundler gem, then follow these steps.

1. Clone the repository

    git clone git://github.com/zonque/AlRide.git

2. cd into the directory

    cd AlRide

3. Install all necessary gems:

    bundle install

If you want to use sqlite in your production environment, make sure to add gem 'sqlite' to the production group of Gemfile before running the bundle command.

4. Create and modify settings:

    cp config/settings/template.yml config/settings.local.yml

In particular, make sure to set the secret token for your application in the settings. rake secret will generate one for you.

5. Create and setup the database

    rake db:setup

6. Precompile assets (only needed for production)

    rake assets:precompile

7. Start the server

To start AlRide in the development environment simply run

    bundle exec rails server

To start AlRide in the production environment make sure you did not skip step 6 and run:

    rails server -e production

(Note that for a "real" production environment you should really use something like unicorn or passenger.)

Navigate to http://localhost:3000/ to use AlRide.

Configuration through environment variables

Environment variables can be used to override settings passed in YAML files such as config/settings.local.yml. Keys must be prefixed with ALRIDE and the nesting separator is __. So for example, in order to set the platform name, you would set the environment variable ALRIDE__platform_name prior to starting the application server.

Heroku

Alternative to host AlRide on your own hardware, you can host AlRide on Heroku. To make this even quicker, click on the button below:

That will setup everything on heroku, all you'll need to provide is the application name and URL.

Customize

The page header on the default welcome screen can be customized by putting Markdown formatted content into a file called config/page_header.<I18n>.md, where <I18n> is one of the supported locale variables (en, de, ...).

If such a files doesn't exist, the configured platform name is shown instead.

Contribute

To contribute, please clone the project and send pull requests through GitHub.

License

All code in this repository is released under the GNU Affero General Public License unless explicitly stated differently. Please refer to the LICENSE file for more detailed information.

TODO

• Add more localizations

• Fix bugs listed in the issue tracker of the GitHub project

alride's Issues

app running, but not posting data, erroring

https://wunderride.herokuapp.com/entries?locale=en

We're sorry, but something went wrong.
If you are the application owner check the logs for more information.

Heroku Auto Deploy - problem with mailgun

Since mailgun has changed their sandbox subdomain policy it doesn't seem to be working without having an own server to set up for this:
https://help.mailgun.com/hc/en-us/articles/217531258
from the logs:
"Net::SMTPFatalError (554 Sandbox subdomains are for test purposes only. Please add your own domain or add the address to authorized recipients in domain settings."

Is there a simple work around or alternative?

Add Travis CI

Once tests are in place (#2), setting up Travis for CI should be simple.

Add tests

There are no tests at the moment. We should add some.

Fix the error display in the 'new' form

When a new entry is created, and it is rejected by the EntriesController, the display of errors in the form is broken.

Month is displayed incorrectly

Offer a ride for 23rd of March, 2022. In the email the date is correct, on the web frontend it's shown as April 23.

Upgrade to Bootstrap 3

There's no urgent need for that, but we should probably try to keep all components as up-to-date as possible.