restrepublic.blogg.se - Filemaker server 13 setup

FILEMAKER SERVER 13 SETUP REGISTRATION
FILEMAKER SERVER 13 SETUP PRO
FILEMAKER SERVER 13 SETUP SOFTWARE
FILEMAKER SERVER 13 SETUP DOWNLOAD
FILEMAKER SERVER 13 SETUP FREE

you can go up in size but you’ll never go back down The image size does not shrink if you delete files from your virtual machine’s hard drive, i.e.

FILEMAKER SERVER 13 SETUP FREE

You’ll need to keep an eye out for your drive running out of free space as your image grows and as you put more files on the drive either in or out of the VM.Dynamic sizing may be more convenient for you, but if you pick this remember two things:.That way I always know the footprint my image will take up I know that I have a large amount of free space on my computer’s drive so I prefer a Fixed Size.

The next screen will ask you how you want to handle the size.

resizing the image if you start to run out of space) using the VirtualBox tools if it’s a VDI format

It’s easier to manipulate the image after the fact (e.g.

FILEMAKER SERVER 13 SETUP SOFTWARE

You’ll likely not use the image with another software.

Using a different format will allow you to more easily use the image with different virtualizing application.

A drop down screen will display asking you which format you want to use.

For our purposes we’ll want to select Create a Virtual Hard Drive now.

Something to keep in mind is that when you give more memory to a virtual machine, you’re creating more overhead for the application running the VM which could possibly slow performance.Ĭreate a Virtual Hard Drive Virtual Box gives you several options as far as specifying what disk your Virtual Machine will use as a hard drive.

Mavericks requires at least 2gb of ram to run so you can leave it at 2048mb or increase it

By default, Virtual Box will allocate 2gb of memory.

On the naming screen, give your VM a name, e.g.

From the menu options, select Machine -> New.

Before you get started make sure you have ruby installed and the iesd gem installed. RubyĪ step in these instructions requires a ruby gem called iesd to allow the virtual machine to use the Mavericks installer as a boot drive.

FILEMAKER SERVER 13 SETUP DOWNLOAD

The Installer will have been download to your Applications folder and named “Install OS X Mavericks”. Once the download is finished the installer will automatically launch. Click “Continue”. Once you’ve logged in with your iCloud account the download will start. You’ll get a message notifying you that Mavericks is already installed on your computer. Once you find OS X Mavericks, click download. Open up the App Store and search for Mavericks. There are several applications you can use: VMWare Fusion (pay), Paralells (pay), and Virtual Box (free). I’ll be using Virtual Box for this demo. To set up your virtual environment you’ll need an application to run the virtual machine.

At least 30gb of free space on your Hard Drive.

Running virtual machines requires a bit of horse power. These specs aren’t required, but they’re strongly suggested: With that out of the way, let’s get into the instructions. This blog post assumes that you’ve already downloaded the installer for FileMaker Server and have your licensing information handy.

FILEMAKER SERVER 13 SETUP PRO

The other caveat, which should be obvious, is you have to own a license for FileMaker Server and you need FileMaker Pro or FileMaker Pro Advanced installed on your local machine. Also, to be able to legally use Mavericks as a virtual machine, you must be on a mac, running mavericks. If enough people tweet me, asking for the windows version, I’ll write another post. I’m more comfortable with nix environments so, I’m writing my outline for a mac setup. To make a virtual development environment for use with FileMaker Server, you have two (2) OS flavor choices: MacOS or Windows. There are plenty of articles out on the web that explain why virtual development environments are advantageous, that’s not what I want to cover. I was really wishing that I could do the same thing with my FileMaker development environment … so I set one up. With tools like vagrant and virtual box, it’s incredibly simple to start up and shut down virtual machines that are tailored to your project.

FILEMAKER SERVER 13 SETUP REGISTRATION

*The registration tool (Registration.Recently, I’ve switched to using virtual machines for almost all of my web development environments and it has been fantastic. *The personalization file Assisted Install.txt *The FileMaker Pro 13.pkg or FileMaker Pro 13 Advanced.pkg installer application I have found that once the initial package is composed properly all subsequent versions of that FM package can be snapshot via Composer, it just requires these bits first: The message you are referencing above is the same message that I received when I hadn't packaged FM13 properly which makes me suspect that FM12 will require similar steps. It was a huge pain because you have to dig into the installer and I think the application itself to find the pieces you need to compose a deployable pkg. When packaging FileMaker 13 (not the same version but maybe the same) I had to follow the instructions found on page 10 here: Packaging FileMaker is actually quite a task.