I am using Hippos CMS 7.9.3 community addition.I am using eclipse as an IDE.Currently we create template on DEV environment and move all repository to test environment , But this will vanish the existing content in Testing environment.Do we have any systematic way in HIPPO CMS either from UI or back-end by which I can incrementally import selected data from one environment to another without hampering the existing data
Hippo CMS has some very decent support for incremental updates to remote instances. In practice, you should never have to remove the remote data to update an instance. The two most commonly used scenarios to get data/content/configuration/code to a remote environment are as follows:
1) You can use the Hippo CMS Console application (http://localhost:8080/cms/console).
It offers an XML export/import functionality, which you can leverage to get changes across. It also offers a diff/patch tool, which allows you to create patches based on your project baseline.
2) For a more automated way, I would advise you to look at content bootstrapping and updater modules.
The online Hippo documentation contains some very decent guidelines/ examples on how the mechanims works and how to do this.
Deploying content and configuration updates
Hippo application release management
Related
I am looking how to deploy the backstage in AWS?
I want to know and understand what we have to do if we want to use service catalog of back stage? do we need to write code any back end services, to use service catalog plug-in
Do we need to create the database or the backstage will create? Who creates the database tables?
What do we do if we ant to add another column to the service catalog?
The docs says the backstage is a mono repo? does that mean do we have both the front end and back end development in single repo?
Is there any need or requirement for Java development if we want to use backstage?
I have a lot of other questions, highly appreciated if anyone is using backstage or want to connect and sharing any insights of using the backstage.
That are a couple of questions, let's see if I can help you.
Do we need to create the database or the backstage will create? Who creates the database tables?
Roadie has a nice intro on running Backstage on AWS Fargate. That includes the steps for provisioning an RDS database. In Backstage, each backend plugin that requires a database is itself responsible for managing the database. You provide only the global credentials and the plugins setup the databases by themself (e.g. creating tables, running migrations for new versions).
What do we do if we ant to add another column to the service catalog?
The database structure of the catalog plugin is quite flexible. If you want to add additional data to it you don't have to modify the database. The Backstage documentation provides some details on extending the data model. To display the data, you have to options: You can either create a plugin that provides new display components to display the value. Or you can change the columns of the catalog table. For that you have to modify your Backstage app a bit. I can't provide the full details as I haven't done it yet, but you can pass custom columns into the <CatalogTable>.
The docs says the backstage is a mono repo? does that mean do we have both the front end and back end development in single repo?
Yes, if you create you new Backstage app with npx #backstage/create-app you get both the frontend and backend, as well as an environment for plugin development in the same folder structure. It should also be all set up the create a running container from that that runs the backend and serves the frontend.
Is there any need or requirement for Java development if we want to use backstage?
No, you don't need Java skills. Backstage is written in TypeScript and React in the frontend and TypeScript, NodeJS, and Express in the backend.
In an online version of draw.io you can enable extra plugins using their url like this https://www.draw.io/?p=svgdata (svgdata is the plugin id)
Is there a way to enable a plugin using Chrome app?
No.
In online version, the Plugins is listed under extras.
In offline as well as in Chrome App, you can't see such an Option
Which means you can't add plugins in the offline version.
Remaining functionalities that you will miss in the offline version
You can’t access or store diagrams using cloud services like Dropbox, GitHub, etc.
Save diagrams to your device or browser instead.
Online help is not available
You can’t insert PlantUML text data.
Math typesetting is not available.
Templates are not available for creating new diagrams.
You can’t export to PDF, but you can print as PDF.
The interface is only available in English.
source : draw.io
Then why?
May be because of issues with caching. If you add many plugins, each of them contains many files. Caching large number of files for offline usage will make the app worst and also consume more memory.
Anyway, you can submit a feature request here
I am finding it difficult locating resources for custom programming, e.g. themes, including and changing JS, altering or adding PHP files, etc.
For instance, does uploading files overwrite installed template files? Like child-themes?
Any pointers appreciated.
For custom programming you are meant to use their API - could I just check you have reviewed the developer documentation here: https://developer.bigcommerce.com/
You are not able to upload server side code like PHP to the big commerce server so it you want to pull Big Commerce data you will need to run the PHP on an external server and then use the Big Commerce API.
Regarding templates, you can create custom templates files by uploading prefixing the template file with an underscore "_" e.g. _CustomCategory.html. By using this approach you will not overwrite the existing template files and your modifications will be easier to maintain in the future.
Apache Ace documentation refers about RepositoryTool.jar that can be used to manage Repository. But I could not find this tool in the Apache ACE distribution. Where can I download this tool?
The page you're referring to is part of the old site (the new one is located at http://ace.apache.org), and refers to tooling you probably shouldn't be using anymore: it has been used before there were other ways to interact with the repository, mainly for development purposes.
Depending on your needs, you can use the repository in a number of ways,
If you need to programmatically read and write the repositories (remember that they're only XML), use the HTTP API available for that.
You can do the same thing from code, see Repository and its implementations.
If you want to edit 'meaningful' ACE data (such as linking distributions and targets), use the Client REST API. This is probably the option you want.
I am building an iOS application which integrates with a Rails CMS. The CMS is running in multiple environments (development, staging, preprod and production). Currently the Info.plist file contains a key that stores a string value which corresponds to and determines which CMS environment the app communicates with. This is not ideal as each time the application needs to be archived for ad-hoc or App Store distribution the value must be changed (which is far too easy to forget). It is also easy to forget to change this value back to development after performing the archive process.
My question is what would be a better approach to control which CMS environment the application communicates with.
The next approach I was thinking of taking was to have the key in the Info.plist point to an environment variable. I could then edit each action of the project's scheme (Run, Test, Archive) in Xcode to set that environment variable as appropriate. The problem with that approach is that the scheme setups are not included in source control. Also only one scheme is used for creating both ad-hoc and App Store archives (which both need to use different CMS environments).