Just installed and started using VSSonarExtension, but already have a couple of questions that I am unable to answer myself:
Why does the extension need to connect to the server if it scans local code with local tools, such as FxCop and StyleCop?
After looking through roughly 15 files, I get an error saying that I need a license to scan more than 15 files in one session - isn't the extension open source?
I want to make sure that the rules specified on the server match the rules locally, so that I get the same output with regards to technical debt - how can I achieve it?
Seems like the extension does not use FxCop, according to the logs; moreover, sometimes logs indicate that some code has been skipped because some rules were not present or defined in StyleCop. What does that mean?
Looking forward to your replies, thanks for help.
answers
so it can sync the quality profile in server, you dont want your users to complain the local analysis is different from what they have in server
local files analysis, is provided by external plugin: please contact support their for details
its the default behaviour. therefore ansering question 1
please open a ticket in github with those issues. it can be that you have some differences between server profile and what is installed locally.
Related
while setting up a basic 1 x NGINX load-balancer in front of 2 backends, I ended up in what it is clear to me to be a bug: the cron of this Certified App cannot be edited:
As you can see, in this particular App the cron file is owned by root:root and doesn't have the extended attribute (the plus on the right of permissions) necessary for the file to be edited also by the logged in user (nginx in this case).
All other certified apps allow instead the main login user to have crontabs, even though I found the permissions of each file vary a lot.
I've stumbled on https://github.com/jelastic/jem/blob/master/etc/jelastic/export.conf and it seems the file to go for proposing a bugfix, but it's last update if Aug-2016, so I guess Jelastic had closed much of its source code.
How can we contribute to Certified App source code?
indeed it is a bug as cron file of nginx user isn't editable in a balancer template, by design in has to be.
As for exports.conf - this file left for backwards comparability, but no more used.
The problem will be definitely fixed in latest templates, as for existing containers - we would like to apply a patch to fix them, if you provide us more details about hosting service provider you are using - we will help with that.
As for contribution to certified templates, all the images are publicly available on Docker Hub, you can create your own version of template based on existing one if you build a docker image and in your Dockerfile you specify
"from jelastic/nginxbalancer" as a base, then you can do any modifications to the filesystem. Next step will be just to replace existing balancer with your custom one.
Anyway, let's start with fix of existing containers.
Many thanks for finding out the bug!
I want to get my Larvel project ready for deployment.
I already found some guides in the web, but no one of them could answer me the following question(s):
Which file do I have to upload to the webserver?
I already tried to remove as much folders/files as possible to keep the project-size on my apache webserver as small as possible. But is there any guide which tells me, which folders/files do i exactly need to exchange?
When it comes to an update:
Once deployed, which files do i need to update?
Do I have to upload all the files again or can I exchange only certain ones?
Currently i followed the official laravel guide and uploaded all files to the webserver.
When I try to deploy a SSAS Tabular project from my local machine to the integration server I get an error in the metadata. It's a many to many error that I had previously solved, and I know I solved it because the Tabular project can be processed locally. That is the crux of the issue, when I process the project, it is using the correct data source, but when I try to deploy the project it uses a previous data source that is no longer valid.
Steps I've taken:
I Went into the model, selected existing connections, and modified them to connect to the correct environment (they were previously pointed at the invalid environment) this allowed me to process the data, but I still can not deploy correctly.
I created a new configuration in the configuration manager, to no avail.
I looked for other areas where the source DB is listed, I haven't found any, which is frustrating because I know it's somewhere.
Is there a cache I'm missing or a setting I didn't check, any help would be appreciated, thank you.
i have a curious issue. When i start the connect manager i see a white window with the following error message: svwrap $Revision: 1.36 $
Error #619 security: script is world-writable
Does anyone have an idea what could be? I know what "world-writable" means but what file it might be? Thanks for an answer. Hermann
I'd contact your hosting company this. This message isn't generated by Magento, it's generated by a program your web hosting company has installed to scan for world writable scripts.
Also, you may want to consider a different web-host if you need to use Magento Connect's web UI. This feature requires the Magento web server user have write access to the Magento installation to download and update files. It sounds like your hosting company may not be down with that.
All that said, my guess is it's, at minimum, the downloader/index.php file.
I tried to deploy my project with capifony, becouse I found here an answer, that with capifony deployment is easy. Well I don't think it is, so my question is:
How can I deploy my project via ftp, I put all my files on the server but even if I browse to web/app.php, the only thing I get is an empty page, whatever route I write in the url. So someone please explain me how can I get this work! Thank you!
A couple of things to think of when deploying a Symfony2 project to a new server or computer (as far as I've encountered) might be:
Make sure that the server and it's PHP installation meets the Symfony2 requirements (and perhaps also the recommendations)
Check that you've somewhat followed the installation instructions (found here)
Try to clear the cache
Make sure that the web server and it's PHP process have write permissions to the cache folder
If none of these helps, try to modify the app_dev.php to temporarily allow access from your current (client) IP (instead of restraining it to localhost). Then, hopefully, you'll get a more useful and detailed error message, instead of the blank page (which often is caused by some fatal error that have occurred during the initialization of the framework and its kernel)
Update: Noticed now that you've tagged your question with 'windows', but that you don't mention which server you're trying to deploy to. I wrote the above with some *nix based server in mind, but hopefully some of it are applicable to Windows servers too (but there might be other common sources of error running under Windows that I'm not familliar with