I want to update my existing FLYWAY setup from community edition to Pro, need step by step process, where do I need to update Pro license in .conf file and also where do I need to update the edition details if it has to be done in .conf file too, is there any other change which needs to be done to use the undo functionality of FLYWAY Pro edition.
There is now an upgrade guide on the Flyway website, which you can see here: https://flywaydb.org/documentation/upgradingToTeams
Excerpt below:
If you are currently using Flyway Community there are a few things you need to do to upgrade to using Flyway Teams. The process to do so differs depending on how you are accessing Flyway, but broadly consists of telling Flyway to use the correct edition, and supplying a license key. See below for more details for each usage.
Related
Preamble
My org is low-risk so we're planning to stick to LTS releases (.NET Core 3.1 at the time of this post.) The Nuget Package Manager Updates list, however, currently offers non-LTS updates (namely to .NET 5.0.)
Question
Is there a way to configure Visual Studio in a way to show LTS updates only? Alternatively, is there any other way I can achieve the same desired result?
(This question is actually almost a copy of Lion's original, but I'm hoping that improvements on api.nuget.org or in the way Visual Studio handles API results may result in a viable answer.)
Your question is a real good question. And many community members want this feature on PackageReference for net core projects.
In fact, what you want is not supported on PackageReference so far. And net framework projects with packages.config nuget management format can realize it. See this official document.
Under packages.config, you can use allowedVersions node for nuget packages on packages.config file, such as [3.1.0, 5.0.0). It means 3.1.0 <= current version < 5.0.0. You can only update the nuget package under that range on the Nuget Package Manager UI.
It is quite useful feature but Microsoft has not added this feature for the new-sdk project with PackageReferece. Therefore, many community members has raised this issue on github which is still in processing.
And the Team has planned to fix the problem on December 20. So I suggest you could follow that github link and add any comments to describe your issue to raise more attention from Microsoft' team. All of them will help solve the problem as soon as possible.
We have seen flyway framework for database migration. It is pretty wonderful. In our project, we are using GuassDB as database which flyway not support yet. Could you please let me kown how to make it work or will GuassDB be supported in future ? Thank you!
There are a few examples if you go through http://github.com/flyway/flyway/pulls - and if you don't mind waiting a day or so we will be adding more detailed instructions to the Flyway website with the 6.2 release. You will be able to find it here:
https://flywaydb.org/documentation/contribute/contributingDatabaseSupport
We generally check DB-Engines ranking to get a feel for the level of support for each database platform before we commit to supporting it, as well as an ability to run our test suite against it.
We've recently had several hacks on our one server. We've been advised to upgrade all scripts. The problem is, the Drupal installations. Upgrading these are a massive task. I would like to know, out of fellow Drupal users, in your experience, how unsafe is it to remain on a say version 6.10 as apposed to upgrading 6.28 (the latest)? Is there a point at which you can say: this is really too old now and an upgrade is absolutely necessary?
I'm not too worried about the modules, my concern is the Core Drupal installation. Does it ever become a security risk, or can you stay on the older versions?
"Upgrading these are a massive task"
Not necessarily! I find using git a pretty safe way to deal with such upgrades.
My basic workflow is usually to:
- create a repository with the current Drupal version.
- download the latest core version
- rsync the current version with the latest core version
- update the repository
As expected, I do all of the above on my local version, after checking that everything is working fine. I update the remote repository, then update the actual live site from git.
If you're not familiar with git, basic tutorials are easy to find online. The idea here is not to explain the process in details, rather to send you in the right direction. You will find that it's a pretty flexible workflow, a great way to update modules and generally any type of code.
I've seen this question but the answers are simply not good enough. I've searched the web and could find a clear listing of the main differences.
I am particularly surprised to see contradictions in the above link, that holds only 4 short answers.
So the question is, beyond support, what are (all) the differences between Alfresco Community and Enterprise editions (for the current versions of course)?
Are there functional or technical features that available in the Enterprise edition, that are not in the community edition?
I find it strange that it's so difficult to get a clear list. Looking at the forums to find this answer is not a serious option from a business perspective.
Until now, I found this link to be useful, but it's from 2009.
In particular, I find the platform support interesting, with the community edition supporting only lamp stuff:
Linux
MySQL
Tomcat
OpenLDAP
Firefox
And the enterprise edition supporting:
Windows
SQL Server
WebLogic, WebSphere
AD/Kerberos
IE and Safari
Apparently, these features are only available in the enterprise edition:
JMX monitoring
Runtime admininstration: What's that exactly? And what's in the community edition then?
Runtime indexing consistency check and update: What's in the community edition then?
High performance and availability: How is that implemented and what's in the community edition then?
Storage policies
Open source and proprietary technology stack support: which ones exaclty? Which ones are supported in the community edition?
If anyone could guide me towards serious documentation about these differences, that would be great.
I also went through the wiki but could not find an answer to my questions in there.
differences between Enterprise and Community vary in detail from version to version and are mainly visible for administrators. We see or maintain both flavors of Alfresco in midsize to very large environments and I would say it's more or less a question of taste and budget what the best decision / edition is for you. Excellent skills in infrastructure and java are highly advisable for both editions to run Alfresco in production.
The technical differences are not as dramatic as not being able to provide very similar functionality for the users - so if you're actually in a decision you should focus on a good technical partner, the support services and maybe the fact that you only get official patches in the Enterprise subscription, not on the Community. BTW Alfresco Enterprise is not Open Source but this is not a real point of interest for most end users. You can access the code as a subscription customer but it is not public available/accessible.
The main differences in features are already named more or less:
Administration
Enterprise has more views and setting in the admin web GUI. In Community you can access most configuration only from the command line. This may be a restriction but in real live Administrators prefer the command line and scripting automation.
Enterprise lets you change some Alfresco settings during runtime (most settings still require restart). Some can be change in the GUI and more in the jmx interface. Also you're able to stop and start subsystems like the CIFS protocol server. We use this feature to switch a system in read only mode. This point is meant with "runtime admininstration". Community requires restart of the service for most configuration changes. It is possible to work around this by advanced scripting like groovy or by implementing modules.
Indexing
Runtime indexing consistency check and update is not a self healing functionality as expected. You will have to learn (at least for now) that you have to recreate the Alfresco index from time to time even in Enterprise environments and that it is better to focus on good strategies how to speed recreation or how to setup standby indexes instead of hunting failed indexing transactions using the check and update methods. For major document model changes you need to recreate the index anyway.
High performance and availability
This is mainly the cluster and replication functionality which is no longer available in Community. It's similar to MS Clusters: It's a lot, lot work for very view more availability since some concepts are missing. The price is high in terms of complexity and can end up in loss of robustness. Even with enterprise support it's a hard job to keep a alfresco cluster running - so you need very good arguments why to go this way. But of course: its possible and available!
High performance: There shouldn't be any difference and if - I'm very curious about the explanation.
Technology stack
The main difference is the database support. In the Community you only can choose between MySQL and Postgres (No Oracle or MS SQL for Community). All other technologies are independent from Enterprise or Community (AD, Kerberos, OS, Browser, ...)
Java Container: I believe over 95% of all Alfresco installations run in tomcat. That's the configuration which is documented, tested and scales. Using WebLogic or WebSphere gives you no added value except new challenges - quite the contrary: You have to solve most issues for yourself and can't benefit from others experience.
Storage policies: I'm not pretty sure and should check in 4.2.x if the Content Store Selector / Storage policies is no longer available in the Community, but it was there in the 3.x versions.
[Edit]: storage policies have been removed in Community 4.2.x:
NoSuchBeanDefinitionException: No bean named 'storeSelectorContentStoreBase' is defined
If there is a really need for this functionality someone may re-enable that feature by coding a module for Community.
Regards
This page explains the difference between the editions:
https://wiki.alfresco.com/wiki/Enterprise_Edition
This page is the canonical, comprehensive list of the differences.
If you are considering an Enterprise Subscription and you have a question that isn't answered by what you can find on that page, you should talk to your account rep.
Well, regarding JMX monitoring:
Runtime administration: Alfresco enterprise allows to perform certain actions on Alfresco subsystems without restarting the server. This allows you to be very fast during debugging/developing and also making changes in production environment. Also you can access the JMX interface that supports JMX Remoting.
There is no consistency check or update, until you restart the server (during the startup you have to validate/check/rebuild your indexes). There is an option in alfresco.global.properties (or the original repository.properties config file) for that. If you have some inconsistencies in the Alfresco Community index, you're gonna have a bad time xD.
Alfresco Enterprise has specific license for clustering your architecture, the Community edition doesn't support those systems. Replicate and cluster Alfresco is one of the main improvements in performance/scalability/availability you could achieve.
The storage policies allow you to use Content Store selectors in Alfresco Enterprise. You can manage a primary and a secondary file store, and map/connect these stores in your architecture. The Community Edition allows you only to use one content store at a time.
These include everything inside Alfresco (Spring Framework, Apache-Lucene/Solr, Tomcat, and so on), because with the Enterprise license you have also the full support with everything inside the Alfresco package. The difference is that the Community is based on daily builds, supported by community, and therefor not guaranteed. The Enterprise support helps you resolve many problems that you might encounter during developing and in production environment, not only Alfresco related, but also on some configurations on supported platforms (Windows/Linux), your web application servers, and so on.
Hope it helps.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Host to use Microsoft Visual SourceSafe or CVS on web hosting for development?
I would start with the question "Why VSS or CVS"? Is this because of a legacy reasons, or is it because you don't know other options?
If the answer is "because of legacy", then you don't have much choices. There are no cloud providers that offer VSS support, and the choices for CVS are not that great either. SourceForge.net still offers CVS support, and searching for "CVS hosting" also yields some results, but most are not well-known names with proven reliability and security.
However, given what your choices are, I would be quite interested to hear more details about a legacy project that uses both VSS and CVS. :-)
If, however, the answer is "because I don't know what else is there", I would strongly recommend to look into SVN, Mercurial or GIT. There are great cloud providers that offer support for these three ranging from free for open source projects to multiple tiers of paid support for proprietary projects. And it's quite easy to set servers for any of these three yourself. Not to mention that all of them are orders of magnitude better than VSS and CVS.
To give you a quick start, here's a short list of providers you can look at:
CodePlex - SVN and Mercurial support, free for open source projects, but there's control over the visibility of your source
GitHub - GIT support, free plans for open source, paid plans for proprietary projects
Google Code - SVN and Mercurial support, free 2GB for open source projects, though they do have some control over the visibility of your source
BitBucket - SVN and Mercurial support, free for 5 users, unlimited for paid and proprietary projects
SourceForge - GIT, SVN, Mercurial, and CVS support, free for open source projects
Unfuddle - GIT and SVN support, paid
CodebaseHQ - GIT, Mercurial and SVN support, paid
There are a lot more out there, with various pricing models (and reliability of course :-))
Update: If you are working on a web app, your web host dos necessarily have to support also the source control. You can have your sources (HTML, CSS, JS) in a separate version control host, and deploy to the web host only the final version of your work.
CVS requires a CVS server to be running (/ available) and I'd be willing the bet that SourceSafe would require the same.
When you get web hosting normally you just get a place to store files and some server software will make it available over http.
I originally thought that this question read "How to use...". Upon double checking the question, "Host to use..." doesn't completely make sense. Hopefully the information I've presented is useful.
You can check out svnhostingcomparison.com for a list of SVN providers.
Use CVS for web development
try cvsdude.com
Just create a stand alone local repository (unless you are on a team, see note below). TortoiseCVS is great for Windows as you can integrate it with the shell and get a right click context sensitive menu. Be sure to add the CVS keywords $RCSfile: $ and $Revision: $ to your HTML files. This will allow you to tell the file(s) name and version that create a web page you are viewing/debugging.
Like this: <!-- $RCSfile: $ $Revision: $ -->
When you check it in CVS will change it to: <!-- $RCSfile: keyword.html,v $ $Revision: 1.3 $ -->.
Here is an online reference:
http://www.badgertronics.com/writings/cvs/index.html
Note: If you are in a dev group you will want a server. There are some security issues, so read the docs. Also, there is an awesome Apache module for CVS that will let you browse and compare code versions. It also colorizes the source, shows who/when changes were made, etc.