I know how to create a partition in local ApacheDS instance from this article. Current problem is I don't know how to create a partition in remote ApacheDS.
I am accessing remote ApacheDS server(in CentOS) from Apache Directory Studio(in Windows).
Any help would be appreciated.
ApacheDS
Version: 2.0.0-M14
Apache Directory Studio
Version: 2.0.0.v20130517
I don't know if your problem is that you can't access the remote instance or another.
But if you want to create a partition follow this "guide".
ApacheDS seems to have a very bad tutorial.
Contrary the other answers, here I explain the real problem. The sad truth is the following:
You can't manipulate the partitions of a non-local Apache Directory Server with Apache Directory Studio.
You can't even do this with a locally running one. The only what you can do, are the Apache Directory Server partitions running inside your Apache Directory Studio.
However, there is a workaround for the problem. It is particularly useful, if you are using linux, or at least you have a cygwin by the hand.
The Apache Directory Server has a complex directory structure, full with small files, partially binary and partially text data.
This data structure doesn't contain any filesystem references, so you can freely clone it.
Create an LDAP server inside your Apache Directory Studio. Open its properties. You get a popup form. Inside this form, you will see some like this:
Location /your/home/directory/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapservers/servers/e56640c7-70ed-4eed-921c-75c475117a11
This is what you want!
This is the directory structure, where your local ApacheDS is running!
And you can now easily synchronize this data structure, ideally with a simple rsync command, into your server or back!
So,
You create the new Apache Directory Server instance inside the Apache Directory Studio
Your check its properties
You stop it, and synchronize your server-side server directory into your this one! For example, rsync -va --delete you#your.server.com:/srv/apacheds/instance/ /your/home/directory/.ApacheDirectoryStudio/.metadata/.plugins/org.apache.directory.studio.ldapservers/servers/e56640c7-70ed-4eed-921c-75c475117a11
You play with the partitions as you wish
You synchronize it back.
Of course if you are playing with the Apache Directory Server file structure on such a low, file-system level, the server needs to be stopped!
Related
I'm currently using H2O steam version 1.1.6 to deploy model endpoints which is working great!
However, steam uses the /tmp directory to store these deploys, which is actually only meant for temporary files. Because the /tmp has been cleared on my server, I've lost some deploys.
Is there a way to change where these files are stored?
Additionally it's also not possible to delete the deployments through the steam UI because the files are gone, is there a way to delete these as well?
I was wrong; the deployments can be found in steam/var/master/model
The files and directories that are located in /tmp are created by jetty.
is it possible to have my magento store on one server and have the store media folder on another server using a symlink?
Would I run into any problems if I was to do this?
I don't have any experience with symlinks and not exactly sure how they work.
You have to mount second server directory on your first server and than you can created symlink for this mounted point. ssfs is the tool I use for mounting.
But I will not recommend doing this because performance wise it will be slower, but in other hand if you can setup any domain/subdomain on that second server then you can provide your remote media url in Magento's system configuration, just like cdn server configuration. And it will enhance performance.
I have a Neo4j database that I initially created using the Neo4j Ruby gem, which uses the embedded server.
In order to deploy my database and accompanying app on Heroku, I need to use Neo4j standalone server's Rest API.
I have tried to switch on my development machine by installing Neo4j server through Homebrew. I edited the libexec/conf/neo4j-server.properties file to point it to the embedded database.
I can start Neo4j server fine, but, when I use the web interface to browse the database, none of my nodes are visible-- only the root node
I know that the server is looking at the correct directory because I can see the correct path in the configuration section of the web interface.
I know the data is still in the database because I can access it from my original Ruby app using the embedded server.
What could be the problem?
I suspect the problem is an issue with relative/absolute paths, meaning you might think it points to the right directory but actually it created an empty database somewhere else. If that's the case, just change your directory settings. As a temporary fix, you can always keep the default settings and just copy your embedded db into the data/graph.db folder. That always works for me.
Checking your path, the thing you need to look for is a leading slash. A leading slash indicates an absolute path, whereas the lack of one indicates a path relative to the main server directory which is the directory that contains conf, bin, data, ... Also, if you typed in the line yourself, check for typos. The correct syntax is:
org.neo4j.server.database.location=/this/is/an/absolute/path
or else this :
org.neo4j.server.database.location=this/is/a/relative/path
I have roughly 200 files that I need to push to our live server after business hours. In addition to this push I have a few database updates that I need to run in conjunction with this roll out.
What has been done in the past on this system is to create a directory on the server of the updated files and create a cron script to copy those files to overwrite their previous versions on the server. And then executing the calls to the database.
Here are the problems I am trying to work around:
1) There is no staging server.
2) There is no easy way to push from our version control (svn) to our live server
3) There are a lot of files and the directory structure is deep so setting up a copy of the directories to be copied over on the server seems precarious and time consuming.
What's the best way to do this?
The way I've done similar things in the past is to have a cron job run a script an administrative machine that:
1) checks out the files I need on my production server on some sort of staging machine
2) rsync's the files onto the server
3) runs a post-rsync script on the server (say via ssh'ing to the server)
However, you specify that you have no ability to use a staging machine, by which I assume you mean that you have no administrative machine at all, and that you cannot check out your repository on the server either. That makes doing this cleanly far harder. Are you sure you can't at least use your workstation or some similar box as an administrative or staging machine here?
My hard-drive has encountered some problems and I am unable to boot Windows with it.
I am able to view the drive's contents by connecting it to another PC as an external drive.
On the culprit drive I was running a local WAMP server for dev purposes and I'm looking to save the mySQL databases from it.
I can see my wamp directory at E:\wamp. Is it possible to start up the server from here so as to use phpmyadmin to perform a mysqldump? If not what are my options to recover the DB-
On my system, they are in C:\Program Files (x86)\WampServer\bin\mysql\mysql5.1.53\data. So in yours they would be in E:\wamp\bin\mysql\mysql-version\data.
You can start mysql locally from E:\wamp\bin\mysql\mysql-version\bin, where all the executables are. Be aware that the configuration file you want to use is E:\wamp\bin\mysql\mysql-version\my.ini.
You can also simply copy all the subdirectories to another server. I'm no MySql expert, but that should let the other server use your databases without problem.
I needed to re-install Wamp and I recovered my databases by copying the data directory in wamp\bin\mysql\mysql-version\ from a backup, phpMyAdmin picked up the databases and tables.