Although the workspace is configured to use localhost everywhere, it is easy to develop against
a remote environment. Either by changing localhost globally with the property installation.host in the project’s root POM file or by customizing some or all of the values listed in the table
below. The property installation.host itself is just a convenience and should only be used within these specialized properties.
| Property | Host of component |
|---|---|
| Content Management Server |
mls.host | Master Live Server |
rls.host | Replication Live Server |
solr.host | Solr search engine |
caefeeder-preview.host | CAE Feeder (preview) |
caefeeder-live.host | CAE Feeder (live) |
studio.host | Studio |
mongo.db.host | Mongo database |
database.host | SQL database |
Table 3.7. Environment properties
If you want to manage multiple environments, you can manage them in your
settings.xml file:
<profile>
<id>dev</id>
<properties>
<cms.host>cms.dev.host.com</cms.host>
<mls.host>cms.dev.host.com</mls.host>
<solr.host>cms.dev.host.com</solr.host>
<database.host>db.dev.host.com</database.host>
<mongo.db.host>mdb.dev.host.com</mongo.db.host>
</properties>
</profile>
<profile>
<id>retest</id>
<properties>
<cms.host>cms.retest.host.com</cms.host>
<mls.host>cms.retest.host.com</mls.host>
<solr.host>cms.retest.host.com</solr.host>
<database.host>db.retest.host.com</database.host>
<mongo.db.host>mdb.retest.host.com</mongo.db.host>
</properties>
</profile>
<profile>
<id>vagrant</id>
<properties>
<cms.host>blueprint</cms.host>
<mls.host>blueprint</mls.host>
<solr.host>blueprint</solr.host>
<database.host>blueprint</database.host>
<mongo.db.host>blueprint</mongo.db.host>
</properties>
</profile>
Example 3.6. Adding Environments in settings.xml
You can choose now to connect to different environments by either manually adding a profile to your
Maven call (such as -Pdev) or by setting the profile permanently in your
settings.xml file.
![[Note]](../common/images/note.png) | Note |
|---|---|
By default, a |
 |  |  |
 |