marketplace_template | open source platform to create your own peer-to-peer

Note: libv8 might fail to build with Clang 7.3, in that case you can try installing V8 manually:. Note: If your MySQL server is configured for SSL, update the config/thinking_sphinx.yml file and uncomment the mysql_ssl_ca lines. Configure correct SSL certificate chain for connection to your database over SSL. Congratulations! Sharetribe should now be up and running for development purposes. Open a browser and go to the server URL (e.g. http://lvh.me:3000). Fill in the form to create a new marketplace and admin user. You should be now able to access your marketplace and modify it from the admin area.
Get the code. Clone this git repository and check out the latest release:
Install the required gems by running the following command in the project root directory:
Install node modules:
Create a database.yml file by copying the example database configuration:
Add your database configuration details to config/database.yml. You will probably only need to fill in the password for the database(s).
Create a config.yml file by copying the example configuration file:
Create and initialize the database:
Run Sphinx index:
Start the Sphinx daemon:
Start the development server: Some components are created with React (see documentation) and they need to be built with Webpack. We have Foreman Procfiles that can be used to run both Rails and Webpack:
React component static build
React component & hot loading styleguide (http://localhost:9001/)
If you need to debug the Rails parts of Sharetribe with Pry, it's not possible with Foreman due to a known compatibility issue. In this case we recommend running Rails with old-fashioned rails server and React builds with Foreman in a separate terminal. That way your binding.pry calls open nicely in the same window with the Rails process.
React component static build, React client only
React component & hot loading styleguide (http://localhost:9001/), React client only
Invoke the delayed job worker in a new console (open the project root folder):
Before starting these steps, perform steps 1-5 from above.
Set secret_key_base
Create the database:
Initialize your database:
Run Sphinx index:
Start the Sphinx daemon:
Precompile the assets:
Invoke the delayed job worker:
In a new console, open the project root folder and start the server:
In your database, change the value of the domain column in the communities table to match the hostname of your domain. For example, if the URL for your marketplace is http://mymarketplace.myhosting.com, then the domain is mymarketplace.myhosting.com.
Change the value of the use_domain column to true (or 1) in the communities table.
Create a IAM role which has full S3 access. Save the AWS access and secret keys.
In the S3 console, create two buckets, one for upload and one for permanent storage. For example your-sharetribe-images and your-sharetribe-images-tmp.
Set the upload bucket (your-sharetribe-images-tmp) to have an expiration (for example, of 14 days) using lifecycle management
Enable CORS on the upload bucket.
Set the following configuration in your sharetribe config.yml: s3_bucket_name: "your-sharetribe-images" s3_upload_bucket_name: "your-sharetribe-images-tmp"
Add your AWS keys to the sharetribe app. The best way to do that is via environment variables, rather than checking them into your config.yml. Set the aws_access_key_id and aws_secret_access_key environment variables to the values for the IAM user.
(Optional) When you enable S3, uploaded images are linked directly to the S3 bucket. If you want to serve these assets through CDN, you can set the user_asset_host configuration option in addition to asset_host in config/config.yml.
if you are having trouble uploading, look at the request using browser devtools and see what error statuses and messages are being sent.
double check that your AWS keys are being correctly set.
if you can upload images successfully, but the images aren't processed, make sure that the delayed-job worker is running.
Use these instructions to set up and deploy Sharetribe for production in different environments. They have been put together by the developer community, and are not officially maintained by the Sharetribe core team. The instructions might be somewhat out of date. If you have installation instructions that you would like to share, don't hesitate to share them at the Sharetribe community forum.
Deploying Sharetribe to Heroku by svallory
See UPGRADE.md for information about actions needed when upgrading. For production use we recommend you to upgrade only when new version is released and not to follow the master branch.