Here you can find a list of questions and answers relating to Movin' In.

Movin' In is free and open source. Movin' In is licensed under the MIT License. The license is permissive. This means that you have lots of permission and few restrictions. You have permission to use the code, to modify it, to publish it, make something with it and sell it, etc.

There are no locked or restricted features. If you deploy Movin' In on your server, you can access all features available.

On demo links provided on GitHub, some features are locked. If you want to unlock these features, contact the project owner by email (requires login).

Movin' In is licensed under the MIT License, which means you can absolutely use it for commercial purposes.

You can:

• Use it in commercial and proprietary products
• Modify and adapt the code as you need
• Distribute your modified or original version
• Use it privately or publicly

Caveats:

• You must include the original license and copyright notice in your distribution
• There is no warranty—you use it at your own risk (this clause protects open-source maintainers from liability while allowing users full freedom to use the software)

There are no other restrictions. It's a very permissive and business-friendly license.

To prevent a property from being booked multiple times when it's already booked, you need to toggle Block Property On Successful Payment option on the property. When enabled (default), the property will not appear in search results if the requested booking times overlap with an existing booking. When disabled, the property can still appear in search results even if it's already booked during that time. In this case, you can manually hide the property by setting it as unavailable from the admin panel.

This option helps manage car availability more easily based on rental policy.

Yes, of course. You can donate through GitHub Sponsorship (one-time or monthly), PayPal, or Buy Me a Coffee. Even a simple star on the GitHub repository helps spread the word and is greatly appreciated.

VITE_MI_HIDE_AGENCIES setting allows to toggle agency visibility in the frontend.

To hide agencies from the frontend, simply set it to true in frontend/.env:

VITE_MI_HIDE_AGENCIES=true

Then re-run the frontend if you are in a development environment or redeploy the frontend if you are in a production environment.

First sign up on brevo: https://www.brevo.com/products/transactional-email/

Second, enter your information, check "I don't have a website" if you don't have one.

Third, enter your address.

Fourth, enter info about your organization and check "I don’t want to receive product updates, marketing tips, or promotional content from Brevo. "

Fifth, enter and validate your phone number.

Finally, you will enter the brevo dashboard.

Click on your organization name on the top right corner, then SMTP & API.

Copy your STMP login email (ex: 8627f603@smtp-brevo.com), and your master password.

Paste your smtp login and master password in api/.env:

MI_SMTP_HOST=smtp-relay.brevo.com
MI_SMTP_PORT=587
MI_SMTP_USER=your-smtp-login@smtp-brevo.com
MI_SMTP_PASS=YOUR_MASTER_PASSWORD
MI_SMTP_FROM=your-email-used-in-sign-up@gmail.com

Once you finished with .env, restart movinin.service:

sudo systemctl restart movinin.service

If you don't want to use the demo database, create an admin user by running the following command from backend to create admin user:

npm run setup

It will create an admin user with the email provided in MI_ADMIN_EMAIL in backend/.env and M00vinin as password. Change the password once you login to the admin panel.

To delete the admin user with the email provided in MI_ADMIN_EMAIL, run the following command from backend:

npm run reset

You can fork the repository, make your changes, and keep your version in sync with the main repository by following the Fork, Customize, and Sync guide.