I created a project using Amber Smalltalk and hosted it on a remote server so multiple people can access it. The network connection is slow and it triggers timeout and just figured that the setting 'waitSeconds' solves the problem.
But, we can't figure out where to set it.The config.js file is generated, and can't be changed manually. Only managed to change it in the default settings in the requirejs source. But that should not be the right place. Please tell me how to solve this problem.
config.js is generated using https://lolg.it/herby/amd-config-builder
from the readme:
The local.amd.json files describe the require.config part for the module at the directory where they are present.
to add WaitSeconds to config.js add it to local.amd.json at the root level of your project.
Related
I'm very new to Rapidoid and I'm experiencing problem with initial configuration of the application. I'm using Rapidoid 5.5.5 with following Rapidoid modules defined in pom:
rapidoid-commons
rapidoid-http-server
rapidoid-web
Java 11 is used to run the application.
I've prepared a custom config-develop.yml file where I've changed value for port to use from default 8080 to 18888 and added some menu items in gui: section however when I start application none of my changes were used: generated log does not have any data about accepting/use of parameters from my file and configuration files are the files that are included into rapidoid-commons Maven artefact.
Also, the log shows that classpath used is limited to /target/classes folder (I'm using Maven as build tool). So, these are my questions:
What are the rules for merging configuration information when multiple config-*.yml files are present in search path?
How I can tell Rapidoid to ignore some configuration files?
Is it possible to specify explicit name for configuration file as part of initialisation process?
I'm happy to provide additional information if this will help to find an answer to the questions above.
With best regards,
Nick
My wish is, that I can build a vue package and install it on any server just by changing the config without recompiling.
My problem:
I don't know how to fetch it.
I use axios for my backend communication at the moment, but I don't know how to download something without knowing the hostname.
I think an ideal solution would be to include a script that contains the config, similar to how the image tag works.
The script should not be minified or included.
But I didn't find a source of anyone doing that (where it worked).
Has anyone a solution for that.
PS: I found this question, but the hostname problem still remains.
My changes are not reflecting inside browser even after storage/framework/views clear and running various artisan clean-up commands.
To make clear that I am calling the right file.
Is it possible my PHP environment is somehow persistent loading this file?
I found the answer.
I am using Nwidart/LaravelModules to structure my project.
Laravel Modules has a command that publishes all modules to the views folder in resources/views. Apparently Laravel was using those 'published modules' alongside the 'official' modules, which caused the problem above.
I have the following set in trac.ini:
[components]
acct_mgr.admin.accountmanageradminpanel = enabled
[inherit]
plugins_dir = ../../plugins
and in a global plugins folder I have TracAccountManager-0.5.dev0-py2.7.egg.
However, I don't see the account manager admin panel still. Putting it in the project specific plugins folder seems to resolve the issue. I'd rather have it be globally inherited. Any ideas?
EDIT:
Forgot to add the following details:
This is on Windows 7, and trac version is 1.2.2.
Let me know if any other details are needed.
EDIT:
It seems to be picking up the plugin b.c. if I go to the admin tab and then manage plugins, the plugin shows up as tracaccountmanager 0.5.dev0. After seeing this, I've confirmed that I do not have a copy of it in the project specific plugins folder.
I've also characterized the inherited plugins dir to be relative to the project env specific plugins dir.
Non-absolute paths are relative to the Environment conf directory. You probably need to modify your relative path. I will update the Trac documentation to specify this detail.
After messing around with the [components] configuration it seems that the documentation for https://trac-hacks.org/wiki/AccountManagerPlugin/Modules#AccountManagerAdminPanel is not working for me. Instead of using
[components]
acct_mgr.admin.AccountManagerAdminPanel = enabled
as the documentation suggests, I'm finding better success using
[components]
acct_mgr.admin.configurationadminpanel = enabled
acct_mgr.admin.useradminpanel = enabled
acct_mgr.api.accountmanager = enabled
acct_mgr.notification.accountchangenotificationadminpanel = enabled
I concluded this from going to the admin plugins section and expanding the tracaccountmanager 0.5.dev0 section, clicking enable all, then started disabling components in batches or individually. In fact, I don't think acct_mgr.admin.AccountManagerAdminPanel does anything from what I've observed.
We are trying to setup stylecop for a team development environment. So far what we have done is:
Checked the files into source control
Create an environment variable on every machine that points to that location (each dev has source checked out to a different location, this solves that)
Add the tag to the project as follows:
This works great, but VS complains that the file is unsafe, and I know to fix that we have to mark is safe in the registry. We wanted to create a .reg file to import this setting and make it easier for everyone. Can we use that environment variable in the path? I have tried the snippet below, but that doesn't seem to work. Is the syntax for an environment variable different?
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\MSBuild\SafeImports]
"StyleCop.4.3"="%StyleCopLocation%\\Microsoft.StyleCop.Targets"
Why you need to host that Targets file in a global place? Everyone can install a copy of StyleCop.
If you in fact plan to share StyleCop settings, please configure the projects to use a project locally setting file (*.SourceAnalysis). You can check in this file along with your projects, and then everyone is in sync.