Further development / Production

[takeyellow]

Hi Geremia,

I would like to congratulate you guys for this application, which could be of help for many people and organisations. I would like to deploy it after some customisations as a free car sharing plateform in our region (Facebook login/registration, itinerary publication, users being able to communicate and arrange for the car sharing details). I am new to Ruby on Rails so I have a couple of worries:

• At this stage, can this application be deployed in production mode. Are there any security issues, can it break at some point and lose all the users database .. etc?

[tagliala]

Hi, thanks

I am new to Ruby on Rails so I have a couple of worries:

Here there are some resources I've found in a tweet yesterday: https://twitter.com/marckohlbrugge/status/1271749844886061059

can this application be deployed in production mode.

Not actually, take a look at the ToDo wiki: https://github.com/diowa/icare/wiki/To-Do

Are there any security issues

None that we know, of course :)

All dependencies are up-to-date, we have @dependabot-bot, Hakiri, Synk, and GitHub's own Security overview to help us watching the repo

For security reasons, the route should be generated by the server, not by the client (ref to the To-Do list)

can it break at some point and lose all the users database

Not by design

[rubydesign]

Hi, I just want to chip in, as i am also looking for an open source car sharing solution. I am a somewhat seasoned developer developer (read: willing and able to chip in) but my question is if you guys have a "strategy" how to handle the sharing vs the pooling. Ie in pooling people share a ride (at the same time). In car sharing, people share a car (using it at different times). Config can probably go a long way, but as there will be quite substantial differences, i am wonder if the main developers are open to this option.