Difference between revisions of "Development environment"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
*Use [[Subversion]] to checkout Archivematica code | *Use [[Subversion]] to checkout Archivematica code | ||
| + | **If you have commit access, use the private repository | ||
**If you have read-only access, use the public [http://code.google.com/p/archivematica/source/browse/trunk#trunk/includes/archivematica GoogleCode repository] | **If you have read-only access, use the public [http://code.google.com/p/archivematica/source/browse/trunk#trunk/includes/archivematica GoogleCode repository] | ||
<pre>svn checkout http://archivematica.googlecode.com/svn/trunk/ archivematica</pre> | <pre>svn checkout http://archivematica.googlecode.com/svn/trunk/ archivematica</pre> | ||
| − | |||
| − | *Run | + | |
| + | *Run localDevSetup scripts. | ||
** /localDevSetup/*.sh | ** /localDevSetup/*.sh | ||
** /localDevSetup/*.sh | ** /localDevSetup/*.sh | ||
** /localDevSetup/*.sh | ** /localDevSetup/*.sh | ||
| + | **This will create links in your local Ubuntu environment back to the relevant Archivematica scripts in your SVN checkout, allowing you to run a local Archivematica version which can continue to pull down revision updates from the code repository | ||
| + | **If you have commit access, you can work on the files in the checkout directory, make changes and commit those back to SVN repository, while also running Archivematica locally to test your changes and commits from other developers. | ||
| + | |||
| + | *Additional local environment configuration | ||
| + | ** ... | ||
| + | ** ... | ||
| + | |||
| + | *Start Archivematica MCP Server & Client | ||
| + | **Open a seperate terminal for each and type: | ||
| + | <pre>...</pre> | ||
| + | <pre>...</pre> | ||
| + | |||
| + | *Start unoconv service (for Open Document format transcoding) | ||
| + | **<pre>...</pre> | ||
| + | |||
| + | *Troubleshooting: if Archivematica freezes (kill command) | ||
| + | <pre>...</pre> | ||
| + | |||
| + | *Troubleshooting: Updates to the Dashboard might require an Apache webserver restart: | ||
| + | </pre>...</pre> | ||
Revision as of 13:25, 3 December 2010
Main Page > Development > Development Environment
This page explains how you can configure an Ubuntu system to use as a basic Archivematica development environment.
- Use Subversion to checkout Archivematica code
- If you have commit access, use the private repository
- If you have read-only access, use the public GoogleCode repository
svn checkout http://archivematica.googlecode.com/svn/trunk/ archivematica
- Run localDevSetup scripts.
- /localDevSetup/*.sh
- /localDevSetup/*.sh
- /localDevSetup/*.sh
- This will create links in your local Ubuntu environment back to the relevant Archivematica scripts in your SVN checkout, allowing you to run a local Archivematica version which can continue to pull down revision updates from the code repository
- If you have commit access, you can work on the files in the checkout directory, make changes and commit those back to SVN repository, while also running Archivematica locally to test your changes and commits from other developers.
- Additional local environment configuration
- ...
- ...
- Start Archivematica MCP Server & Client
- Open a seperate terminal for each and type:
...
...
- Start unoconv service (for Open Document format transcoding)
...
- Troubleshooting: if Archivematica freezes (kill command)
...
- Troubleshooting: Updates to the Dashboard might require an Apache webserver restart:
...