You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to know if there would be a way to start the aerospike-server container and automatically restore a dump after the server has started.
My goal is to provide an easy way for developers to start the container with a dump from staging or production (mounted as volume or burnt into a custom image), so that they can work locally with a dataset from one of these environment.
I have not find anything in the entrypoint that could make this possible.
I know that official Postgresql or mongodb images provide this kind of feature, as you can run a script or load a dump that is located in a folder like /docker-entrypoint-initdb.d. The script is run after the server is started so that you can automate any task, such as a database restore, create users , etc ..., when the container starts.
Is a feature like this planned in the future ?
Or could you provide some guidance in order to achieve this ?
Thank you for your help
The text was updated successfully, but these errors were encountered:
This is more of a docker automation in running a script post startup. This could be a shell script that runs asbackup and asrestore inline. Please see Section 5-3:
Hi,
I would like to know if there would be a way to start the aerospike-server container and automatically restore a dump after the server has started.
My goal is to provide an easy way for developers to start the container with a dump from staging or production (mounted as volume or burnt into a custom image), so that they can work locally with a dataset from one of these environment.
I have not find anything in the entrypoint that could make this possible.
I know that official Postgresql or mongodb images provide this kind of feature, as you can run a script or load a dump that is located in a folder like /docker-entrypoint-initdb.d. The script is run after the server is started so that you can automate any task, such as a database restore, create users , etc ..., when the container starts.
Is a feature like this planned in the future ?
Or could you provide some guidance in order to achieve this ?
Thank you for your help
The text was updated successfully, but these errors were encountered: