![]() ![]() And if that list of base modules ever changes in the future it could break your workflow. It is also possible to specify a list of modules (in JSON format) in that argument, but I don’t really recommend that because you need to make sure that you include all the individual base modules in the list otherwise farmOS might not work correctly. It works as follows:ĭrush site-install farm farm.modules='all'ĭrush site-install farm farm.modules='default'ĭrush site-install farm farm.modules='base' One other tip I can share: farmOS provides a shortcut/helper for selecting which farmOS-specific modules get installed during drush site-install, which may be helpful to you. If you find a good set of commands that work, please share them so we can learn I think your commands are only downloading translations for the farmOS profile, but not for all other core/contrib translations? There may be Drush commands that can accomplish many of the same things. That is the only way that I’ve tested things, so I can’t speak to other approaches. Welcome to the forum just wanted to add the link to our official docs for setting up translations, if you haven’t already seen them: Translating farmOS | farmOS
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |