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 16.04 or later with:
30 sudo apt-get install ruby2.5 libruby2.5 ruby2.5-dev \
31 libmagickwand-dev libxml2-dev libxslt1-dev nodejs \
32 apache2 apache2-dev build-essential git-core \
33 postgresql postgresql-contrib libpq-dev postgresql-server-dev-all \
34 libsasl2-dev imagemagick libffi-dev
35 sudo gem2.5 install bundler
38 ### Alternative platforms
42 For Fedora, you can install the minimum requirements with:
45 sudo yum install ruby ruby-devel rubygem-rdoc rubygem-bundler rubygems \
48 postgresql postgresql-server postgresql-contrib postgresql-devel \
49 perl-podlators ImageMagick libffi-devel
52 If you didn't already have PostgreSQL installed then create a PostgreSQL instance and start the server:
55 sudo postgresql-setup initdb
56 sudo systemctl start postgresql.service
59 Optionally set PostgreSQL to start on boot:
62 sudo systemctl enable postgresql.service
67 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.
69 Installing PostgreSQL:
71 * Install Postgres.app from https://postgresapp.com/
72 * Add PostgreSQL to your path, by editing your profile:
78 `export PATH=/Applications/Postgres.app/Contents/MacOS/bin:$PATH`
80 Installing other dependencies:
82 * Install Homebrew from https://brew.sh/
83 * Install the latest version of Ruby: `brew install ruby`
84 * Install ImageMagick: `brew install imagemagick`
85 * Install libxml2: `brew install libxml2 --with-xml2-config`
86 * If you want to run the tests, you need `phantomjs` as well: `brew install phantomjs`
87 * Install Bundler: `gem install bundler`
89 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.
91 ## Cloning the repository
93 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:
96 git clone https://github.com/openstreetmap/openstreetmap-website.git
99 To clone only the most recent version (~23MB), instead use a 'shallow clone':
102 git clone --depth=1 https://github.com/openstreetmap/openstreetmap-website.git
105 If you want to add in the full history later on, perhaps to run `git blame` or `git log`, run `git fetch --depth=1000000`
110 We use [Bundler](http://gembundler.com/) to manage the rubygems required for the project.
113 cd openstreetmap-website
119 The Rails Port uses three databases - one for development, one for testing, and one for production. The database-specific configuration
120 options are stored in `config/database.yml`, which we need to create from the example template.
123 cp config/example.database.yml config/database.yml
126 PostgreSQL is configured to, by default, accept local connections without requiring a username or password. This is fine for development.
127 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
128 instructions below as appropriate.
130 ### PostgreSQL account setup
132 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.
136 createuser -s <username>
140 ### Create the databases
142 To create the three databases - for development, testing and production - run:
145 bundle exec rake db:create
148 ### PostgreSQL Btree-gist Extension
150 We need to load the `btree-gist` extension, which is needed for showing changesets on the history tab.
153 psql -d openstreetmap -c "CREATE EXTENSION btree_gist"
156 ### PostgreSQL Functions
158 We need to install special functions into the PostgreSQL databases, and these are provided by a library that needs compiling first.
166 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.
169 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"
170 psql -d openstreetmap -c "CREATE FUNCTION tile_for_point(int4, int4) RETURNS int8 AS '`pwd`/db/functions/libpgosm', 'tile_for_point' LANGUAGE C STRICT"
171 psql -d openstreetmap -c "CREATE FUNCTION xid_to_int4(xid) RETURNS int4 AS '`pwd`/db/functions/libpgosm', 'xid_to_int4' LANGUAGE C STRICT"
174 ### Database structure
176 To create all the tables, indexes and constraints, run:
179 bundle exec rake db:migrate
184 To ensure that everything is set up properly, you should now run:
187 bundle exec rake test:db
190 This test will take a few minutes, reporting tests run, assertions, and any errors. If you receive no errors, then your installation is successful.
192 The unit tests may output parser errors related to "Attribute lat redefined." These can be ignored.
194 ### Starting the server
196 Rails comes with a built-in webserver, so that you can test on your own machine without needing a server. Run
199 bundle exec rails server
202 You can now view the site in your favourite web-browser at `http://localhost:3000/`
204 Note that the OSM map tiles you see aren't created from your local database - they are just the standard map tiles.
208 After installing this software, you may need to carry out some [configuration steps](CONFIGURE.md), depending on your tasks.