I think the page that you propose creating would be very helpful. I have
been using DSpace for about 3 months. I would have found such an overview
very helpful.
Here is a summary of the process that I am using, and it has proven to be
very helpful so far.
I will be glad to share more details if the wiki page you propose is
created.
- Setup
- Download DSpace release to development machine
- Add code directories to source code management (exclude target
dirs, data dirs and log dirs from source code)
- Create a config file for each environment
- dspace.cfg.local: Developer desktop
- use unique sub-handle for resources created in this domain to
avoid handle collision with the production repository
- dspace.cfg.dev: Build/integration machine
- use unique sub-handle for resources created in this domain
to avoid handle collision with the production repository
- dspace.cfg.test: System test machine
- use unique sub-handle for resources created in this domain
to avoid handle collision with the production repository
- dspace.cfg.prod: Production machine
- Modify configuration settings in the config directory
- When applicable, add custom overlays and themes to the modules
directory
- If applicable, reference any 3rd party packages in maven build
file. Add corresponding credentials to local maven repository.
- Run maven build from [dspace-src]/dspace
- mvn package
- Run ant build from the target/dspace... directory using the local
config file
- ant -Dconfig=congig\dspace.cfg.local -Doverwrite=true update
- Restart tomcat
- Unit test customizations
- Commit changes to source code repository
- Build/Integration machine
- Create build script to
- Delete build directory
- Extract code from code repository
- Run maven build
- Add credentials for 3rd party modules if needed
- Run ant build using DEV config file
- ant -Dconfig=congig\dspace.cfg.dev -Doverwrite=true update
- Run script to modify config file with host-specific settings not
stored in source code repository (i.e. database passwords)
- Tar up the target directory and save as a baseline tar file
- Restart tomcat (and apache if applicable)
- Execute build script
- System Test machine
- Create build script to
-
- Extract target directory from baseline tar file
- Run ant build using TEST config file
- ant -Dconfig=congig\dspace.cfg.test -Doverwrite=true update
- Run script to modify config file with host-specific settings not
stored in source code repository (i.e. database passwords)
- Copy baseline tar file to System Test machine
- Execute build script
- Restart tomcat (and apache if applicable)
- Production machine
- Create build script to
-
- Extract target directory from baseline tar file
- Run ant build using PRODconfig file
- ant -Dconfig=congig\dspace.cfg.prod -Doverwrite=true update
- Run script to modify config file with host-specific settings not
stored in source code repository (i.e. database passwords)
- Copy baseline tar file to Production machine
- Execute build script
- Restart tomcat (and apache if applicable)
Data synchronization strategy
- I am manually copying data from production to my other environments on
an as-needed basis
- I have not yet scripted the data copy process
On Tue, Sep 18, 2012 at 10:02 AM, helix84 <heli...@centrum.sk> wrote:
> Ben, would you care to document your practices on a wiki page? We
> don't have such page yet, it could be very useful for some beginners.
> Especially the processes and techniques for moving code from
> dev->staging->prod; are you using git branches? patches? shared
> directories? rsync? How often do you move code from dev to staging?
> How and how long are you testing code on staging before you move to
> prod? Who participates in testing? How do you guarantee that the
> staging environment is the same as in prod? just regular OS updates?
> VM cloning? how often? What automation tools do you use?
>
> Regards,
> ~~helix84
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
--
Terry Brady
Applications Programmer Analyst
Lauinger Information Technology
202-687-7053
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
