These are chat archives for mirumee/saleor
saleor.readthedocs.ioand have set
AWS_STORAGE_BUCKET_NAMEMy site is in production But on image upload it open my local machine directory and when I update, it gives
Server Error (500).
For example, I've added within the product form page: <form id=id_custom_text>. But in my response.POST data I'm only getting
@stephenmoloney Django settings are loaded at the start and are supposed to be immutable. For dynamic settings we are using
SiteSettings instance that can be modified on the fly. You can use
DJANGO_SETTINGS_MODULE env variable to point to a different settings file.
Celery is used mostly for asynchronous actions, like sending emails, generating thumbnails and analytics
Static folder is loaded at the server start and not supposed to be changed afterwards, all of the user-generated content goes into the
SECRET_KEYpermanently to your os environment settings, I don't recommend changing that in the
settings.pyfile directly as it could be easily overridden by an accident
STATIC_URLenv variable to be used by the webpack?
@stephenmoloney Totally agree with your point of view on the upcoming changes. At some point we want to completely split the logic between different repositories, new storefront will be started as a separate repo for sure, I think that we will keep backend + dashboard logic at mirumee/saleor for now.
Some sort of
saleor-cli would be helpful in glueing it all together, but that's still a problem we will need to face in the near future.
[Mon Aug 20 01:20:02.668899 2018] [wsgi:error] [pid 9539:tid 139933306869504] [remote 188.8.131.52:6909] return self._save(name, content) [Mon Aug 20 01:20:02.668902 2018] [wsgi:error] [pid 9539:tid 139933306869504] [remote 184.108.40.206:6909] File "/home/googleuser/ecom/ecom/lib/python3.6/site-packages/django/core/files/storage.py", line 236, in _save [Mon Aug 20 01:20:02.668905 2018] [wsgi:error] [pid 9539:tid 139933306869504] [remote 220.127.116.11:6909] os.makedirs(directory) [Mon Aug 20 01:20:02.668907 2018] [wsgi:error] [pid 9539:tid 139933306869504] [remote 18.104.22.168:6909] File "/home/googleuser/ecom/ecom/lib/python3.6/os.py", line 210, in makedirs [Mon Aug 20 01:20:02.668910 2018] [wsgi:error] [pid 9539:tid 139933306869504] [remote 22.214.171.124:6909] makedirs(head, mode, exist_ok) [Mon Aug 20 01:20:02.668912 2018] [wsgi:error] [pid 9539:tid 139933306869504] [remote 126.96.36.199:6909] File "/home/googleuser/ecom/ecom/lib/python3.6/os.py", line 220, in makedirs [Mon Aug 20 01:20:02.668915 2018] [wsgi:error] [pid 9539:tid 139933306869504] [remote 188.8.131.52:6909] mkdir(name, mode) [Mon Aug 20 01:20:02.668927 2018] [wsgi:error] [pid 9539:tid 139933306869504] [remote 184.108.40.206:6909] PermissionError: [Errno 13] Permission denied: '/home/googleuser/ecom/saleor/media' [Mon Aug 20 01:20:02.668940 2018] [wsgi:error] [pid 9539:tid 139933306869504] [remote 220.127.116.11:6909]
PermissionError: [Errno 13] Permission denied: '/home/googleuser/ecom/saleor/media'
saleor/mediait lets me upload images but they are not displayed on site and they are not getting added in my s3 bucket
If you want to upload media to s3 bucket, then you should set the appropriate env variables in the first place, take a look at the
Serving media files with a S3 bucket section in the https://saleor.readthedocs.io/en/latest/deployment/s3.html
Right now it looks like you've created a new folder and didn't set the proper ownership for the folder and it's files (can be done with
chown command on unix systems)
git checkout dashboard-2.0or wait, thoughts ?
ENV PROCESSES 4tells it to spawn 4 workers i presume
uwsgineed 4 workers ? is one worker per client connection ?
The workers are their to improve the concurrency, thus the throughput.
uwsgi is (pre)forking the WSGI application at launch time and dispatch the requests to the workers that will serve it. As the fork process is heavy, instead of forking on demand (e.g.: in some implement of fastcgi, they would fork the application whenever a request was made, as long as the number of concurrent process is respected, which is time consuming).
You can also set a number of thread per process (
workers * threads), which are spawned inside the worker whenever a request is done. Depending on the resources you have on your server (mostly memory), you may or may not prefer threads as they are lighter.
this will define the allocation per pod
resources: requests: cpu: memory: limits: cpu: memory
values.yamlso I will try to make it as configurable as possible. So if someone wanted:
As of now, you would have to edit the core.
and our client wants a custom Payment provider as well.
Depends what you mean by "custom", if it is a non already implemented payment provider, you would have to implement it which would be fairly quick and easy to do. You have the list of the existing providers here and two more here, in addition to razorpay.