These are chat archives for locomotivecms/v3

10th
Jan 2017
jordan
@jshih
Jan 10 17:10
Hi all, is there any way to force assets of any file type to deploy V3? I was able to do this back in V2. Is there some type of "whitelist" system that has all the current file types, and where you can add more?
Didier Lafforgue
@did
Jan 10 17:12
hi @jshih!
theme assets you mean?
jordan
@jshih
Jan 10 17:14
yes!
thanks for the quick response
Didier Lafforgue
@did
Jan 10 17:14
for the extension of your files?
jordan
@jshih
Jan 10 17:14
yes, i have a .eps file of a theme logo that is being used, amongst other files
Didier Lafforgue
@did
Jan 10 17:14
(are u trying to deploy theme assets on locomotive.works?)
jordan
@jshih
Jan 10 17:14
deploying to my own engine locally so far
i'm trying to upgrade to V3
Didier Lafforgue
@did
Jan 10 17:15
well, 2 things
1/ .eps is not a theme asset in my point of view
jordan
@jshih
Jan 10 17:15
do you think that should be stored elsewhere and referenced instead?
the way that designer designed the site, I can't help but use those assets
however, it is references in the CSS stylesheet
so I'm not sure how I would go about it if i'm not able to upload it as a theme asset
referenced*
Didier Lafforgue
@did
Jan 10 17:17
2/ if you REALLY want to upload it as a theme asset, then re-open the ThemeAssetUploader class in your Rails app (https://github.com/locomotivecms/engine/blob/master/app/uploaders/locomotive/theme_asset_uploader.rb#L13).
your .eps file won’t be displayed in all the browsers
jordan
@jshih
Jan 10 17:18
yeah that's a problem for the designer :/
I'm open to suggestions that don't involve overriding the Engine
Didier Lafforgue
@did
Jan 10 17:18
is it a logo?
jordan
@jshih
Jan 10 17:18
yes
Didier Lafforgue
@did
Jan 10 17:19
he/she has to convert it into a SVG file instead (or a png)
jordan
@jshih
Jan 10 17:20
well, first let me explain how I got to this point. My V2 site for my client for some reason has been acting weird -- I wasn't able to login, the index page said "Content of home page" or something like that. i restored the site from a backup and within 24 hrs the same thing happened again. all user accts were changed within that time as well
Didier Lafforgue
@did
Jan 10 17:20
hmmmm
jordan
@jshih
Jan 10 17:20
it had been acting fine for a solid 2 years
Didier Lafforgue
@did
Jan 10 17:20
what changed?
jordan
@jshih
Jan 10 17:20
nothing
do you know if there is any vulnerabilites or anything like that?
it seems like the DB could have been wiped, would that explain it?
the engine is hosted on a DigitalOcean droplet
Didier Lafforgue
@did
Jan 10 17:21
doesn’t make sense
jordan
@jshih
Jan 10 17:21
it's been stable for a good 2 years
Didier Lafforgue
@did
Jan 10 17:21
hmmm
jordan
@jshih
Jan 10 17:21
overnight, the site just completely erases itself or could have been compromised
no one has accessed the droplet
user accts were different
Didier Lafforgue
@did
Jan 10 17:22
what do your app logs say?
jordan
@jshih
Jan 10 17:22
could it be a mongodb problem?
Didier Lafforgue
@did
Jan 10 17:22
we’ve been running locomotive v2.5.x on our old hosting platform for 3 or 4 years now
working great
jordan
@jshih
Jan 10 17:23
yeah it's been solid for us too, it's a good platform i'm just really confused about what could be causing it
thanks for your work on it
Didier Lafforgue
@did
Jan 10 17:23
could it be an automatic restore procedure?
jordan
@jshih
Jan 10 17:23
no, there's no reason that should be happening
Didier Lafforgue
@did
Jan 10 17:23
(you’re welcome)
jordan
@jshih
Jan 10 17:23
what's the best way to handle logging?
i didn't have any logs unfortunately and given the time I had to get site back up I just restored the snapshot
i'm going to keep the V2 site running for now but I would like to see if there's some way to log what happens if it happens again today/tonight
I was also trying to set up a new V3 site and that's when I ran into the assets problem.
Didier Lafforgue
@did
Jan 10 17:24
well you should have checked your production.log file
if you can point the moment when the changes happen that’d be a great step
jordan
@jshih
Jan 10 17:26
for sure, that's an error on my part for not checking the production logs
Didier Lafforgue
@did
Jan 10 17:27
you needed to restore the platform asap :-(
jordan
@jshih
Jan 10 17:33
i took out the undesirable files and it deployed fine. It looks like it'll be fine :) hopefully V3 can be up and running without problems . thanks for your help and quick response
Didier Lafforgue
@did
Jan 10 17:35
you’re welcome!
keep me posted about your strange DB
:-)
jordan
@jshih
Jan 10 17:36
i will!
jordan
@jshih
Jan 10 19:56
hey Didier, it just happened again on the V2 site: I'm not very good at deciphering logs, could I send it to you privately?
Didier Lafforgue
@did
Jan 10 20:58
sure
did at locomotivecms dot com
jordan
@jshih
Jan 10 20:58
awesome :) thanks so much
i just e-mailed it
Didier Lafforgue
@did
Jan 10 22:20
@jshih
looking at it right now