3 These instructions are designed for setting up The Rails Port for development and testing.
4 If you want to deploy the software for your own project, then see the notes at the end.
6 You can install the software directly on your machine, which is the traditional and probably best-supported approach. However, there is an alternative which may be easier: Vagrant. This installs the software into a virtual machine, which makes it easier to get a consistent development environment and may avoid installation difficulties. For Vagrant instructions, see [VAGRANT.md](VAGRANT.md).
8 These instructions are based on Ubuntu 18.04 LTS, which is the platform used by the OSMF servers.
9 The instructions also work, with only minor amendments, for all other current Ubuntu releases, Fedora and MacOSX
11 We don't recommend attempting to develop or deploy this software on Windows. If you need to use Windows, then try developing this software using Ubuntu in a virtual machine, or use [Vagrant](VAGRANT.md).
15 Many of the dependencies are managed through the standard Ruby on Rails mechanisms -
16 i.e. ruby gems specified in the Gemfile and installed using bundler. However, there are a large number
17 of packages required before you can get the various gems installed.
19 ## Minimum requirements
27 These can be installed on Ubuntu 18.04 or later with:
31 sudo apt-get install ruby2.5 libruby2.5 ruby2.5-dev bundler \
32 libmagickwand-dev libxml2-dev libxslt1-dev nodejs \
33 apache2 apache2-dev build-essential git-core phantomjs \
34 postgresql postgresql-contrib libpq-dev postgresql-server-dev-all \
35 libsasl2-dev imagemagick libffi-dev libgd-dev libarchive-dev libbz2-dev
36 sudo gem2.5 install bundler
39 ### Alternative platforms
43 For Fedora, you can install the minimum requirements with:
46 sudo dnf install ruby ruby-devel rubygem-rdoc rubygem-bundler rubygems \
49 postgresql postgresql-server postgresql-contrib postgresql-devel \
50 perl-podlators ImageMagick libffi-devel gd-devel libarchive-devel \
51 bzip2-devel nodejs-yarn
54 If you didn't already have PostgreSQL installed then create a PostgreSQL instance and start the server:
57 sudo postgresql-setup initdb
58 sudo systemctl start postgresql.service
61 Optionally set PostgreSQL to start on boot:
64 sudo systemctl enable postgresql.service
69 For MacOSX, you will need XCode installed from the Mac App Store; OS X 10.7 (Lion) or later; and some familiarity with Unix development via the Terminal.
71 Installing PostgreSQL:
73 * Install Postgres.app from https://postgresapp.com/
74 * Make sure that you've initialized and started Postgresql from the app (there should be a little elephant icon in your systray).
75 * Add PostgreSQL to your path, by editing your profile:
81 `export PATH=/Applications/Postgres.app/Contents/MacOS/bin:$PATH`
83 After this, you may need to start a new shell window, or source the profile again by running `. ~/.profile`.
85 Installing other dependencies:
87 * Install Homebrew from https://brew.sh/
88 * Install the latest version of Ruby: `brew install ruby`
89 * Install ImageMagick: `brew install imagemagick`
90 * Install libxml2: `brew install libxml2`
91 * Install libgd: `brew install gd`
92 * Install Yarn: `brew install yarn`
93 * Install pngcrush: `brew install pngcrush`
94 * Install optipng: `brew install optipng`
95 * Install pngquant: `brew install pngquant`
96 * Install jhead: `brew install jhead`
97 * Install jpegoptim: `brew install jpegoptim`
98 * Install gifsicle: `brew install gifsicle`
99 * Install svgo: `brew install svgo`
100 * Install Bundler: `gem install bundler` (you might need to `sudo gem install bundler` if you get an error about permissions)
102 You will need to tell `bundler` that `libxml2` is installed in a Homebrew location. If it uses the system-installed one then you will get errors installing the `libxml-ruby` gem later on.
105 bundle config build.libxml-ruby --with-xml2-config=/usr/local/opt/libxml2/bin/xml2-config
108 If you want to run the tests, you need `phantomjs` as well:
111 brew tap homebrew/cask
112 brew cask install phantomjs
115 Note that OS X does not have a /home directory by default, so if you are using the GPX functions, you will need to change the directories specified in config/application.yml.
117 ## Cloning the repository
119 The repository is reasonably large (~150MB) and it's unlikely that you need the full history. If you are happy to wait for it all to download, run:
122 git clone https://github.com/openstreetmap/openstreetmap-website.git
125 To clone only the most recent version (~23MB), instead use a 'shallow clone':
128 git clone --depth=1 https://github.com/openstreetmap/openstreetmap-website.git
131 If you want to add in the full history later on, perhaps to run `git blame` or `git log`, run `git fetch --depth=1000000`
136 We use [Bundler](http://gembundler.com/) to manage the rubygems required for the project.
139 cd openstreetmap-website
145 We use [Yarn](https://yarnpkg.com/) to manage the Node.js modules required for the project.
148 bundle exec rake yarn:install
151 ## Prepare local settings file
153 This is a workaround. [See issues/2185 for details](https://github.com/openstreetmap/openstreetmap-website/issues/2185#issuecomment-508676026).
156 touch config/settings.local.yml
161 The Rails port needs to be configured with an object storage facility - for
162 development and testing purposes you can use the example configuration:
165 cp config/example.storage.yml config/storage.yml
170 The Rails Port uses three databases - one for development, one for testing, and one for production. The database-specific configuration
171 options are stored in `config/database.yml`, which we need to create from the example template.
174 cp config/example.database.yml config/database.yml
177 PostgreSQL is configured to, by default, accept local connections without requiring a username or password. This is fine for development.
178 If you wish to set up your database differently, then you should change the values found in the `config/database.yml` file, and amend the
179 instructions below as appropriate.
181 ### PostgreSQL account setup
183 We need to create a PostgreSQL role (i.e. user account) for your current user, and it needs to be a superuser so that we can create more databases.
187 createuser -s <username>
191 ### Create the databases
193 To create the three databases - for development, testing and production - run:
196 bundle exec rake db:create
199 ### PostgreSQL Btree-gist Extension
201 We need to load the `btree-gist` extension, which is needed for showing changesets on the history tab.
204 psql -d openstreetmap -c "CREATE EXTENSION btree_gist"
207 ### PostgreSQL Functions
209 We need to install special functions into the PostgreSQL databases, and these are provided by a library that needs compiling first.
217 Then we create the functions within each database. We're using `pwd` to substitute in the current working directory, since PostgreSQL needs the full path.
220 psql -d openstreetmap -c "CREATE FUNCTION maptile_for_point(int8, int8, int4) RETURNS int4 AS '`pwd`/db/functions/libpgosm', 'maptile_for_point' LANGUAGE C STRICT"
221 psql -d openstreetmap -c "CREATE FUNCTION tile_for_point(int4, int4) RETURNS int8 AS '`pwd`/db/functions/libpgosm', 'tile_for_point' LANGUAGE C STRICT"
222 psql -d openstreetmap -c "CREATE FUNCTION xid_to_int4(xid) RETURNS int4 AS '`pwd`/db/functions/libpgosm', 'xid_to_int4' LANGUAGE C STRICT"
225 ### Database structure
227 To create all the tables, indexes and constraints, run:
230 bundle exec rake db:migrate
235 To ensure that everything is set up properly, you should now run:
238 bundle exec rake test:db
241 This test will take a few minutes, reporting tests run, assertions, and any errors. If you receive no errors, then your installation is successful.
243 The unit tests may output parser errors related to "Attribute lat redefined." These can be ignored.
245 ### Starting the server
247 Rails comes with a built-in webserver, so that you can test on your own machine without needing a server. Run
250 bundle exec rails server
253 You can now view the site in your favourite web-browser at [http://localhost:3000/](http://localhost:3000/)
255 Note that the OSM map tiles you see aren't created from your local database - they are just the standard map tiles.
259 After installing this software, you may need to carry out some [configuration steps](CONFIGURE.md), depending on your tasks.