You are viewing limited content. For full access, please sign in.

Question

Question

Development Environment Guide

asked on May 31, 2019

Is there any updated information regarding the best practices for creating a development environment? What is the starting step? 

I did see a few questions on the same topic, but not much information.

0 0

Replies

replied on May 31, 2019

Ideally you want the configuration of any non-production environments to match your production environment as closely as possible. This will reduce the friction of moving solutions from one environment to another and help reduce the number of surprises.

0 1
replied on May 31, 2019

I think this goes without saying. I'm looking for a bit more specific information

1 0
replied on May 31, 2019

It's a very vague question. Please provide some more specific things that you are looking to learn.

Our test/development environment is simply as close of a replica to production as we can get, short of replicating the actual data. To test specific scenarios we sometimes attach a copy of the production repository database and point it to an empty directory. The repository works just fine without having access to the files. Otherwise, we'll briefcase across specific folder structures for certain processes.

1 0
replied on June 3, 2019

yes, it is a vague question. I am not the person that installed the LF suite, but now I need to create a development environment. Where should I start? 

0 0
replied on June 4, 2019

Ouch! That is painful to have to figure out where somebody left off. As far as configuring the Laserfiche server, you probably just need to walk through the configuration of the existing components (aside from the repository, we'll get to that). If you can install a new server that closely matches that configuration, you'll be most of the way there.

That will include, installing the Laserfiche Server and probably Workflow. Depending on your environment, you may have to install Web Access, and WebLink. There are pretty good references in the documentation for the specific install steps. There isn't right now a good way to replicate licensing, so you'll need to license the dev server with your existing license infrastructure.

Once you have LFS running, you can create a repository that matches the existing configuration. You can walk through them both and make sure that the dev repository is configured the same. The reason I mentioned leaving that until later is because it's pretty easy to get LFS working. Most of the detail is in the repository.

There's a lot of details here. Please don't hesitate to ask about specific pieces as you get to them.

1 0
replied on June 4, 2019

Thanks a bunch! Will reach out if needed

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.