Quantcast
Channel: Superdesk Development Discussions on Sourcefabric Forum
Viewing all 288 articles
Browse latest View live

exiftoll

$
0
0
Guys, I'm having problems encodig utf-8 in superdesk because Exif does not support my language ..

The solution would be to exchange Exif for Exiftool - someone has already made this change that can post here in the forum.

Help with installation of Superdesk

Ingest issue

$
0
0
I have Superdesk up and running but for some reason it is not ingesting anything. Has anyone else had this issue? Is there a port I need to open for this to happen? 

How to restart Superdesk

Live view not available on Timline Pane

Sending User Notification Emails Not Working

$
0
0
I  have tried all day to get an email sent from Superdesk to no avail.  I have tried numerous methods.

First, I reinstalled my Ubuntu 16.04 OS and did a clean Superdesk install using the curl method found in the git documentation

I started setting up users and tried to send activation emails but nobody received the emails.  I checked the logs and it was reported that the emails were created and sent.  I then monitored all traffic going out of port 25 (which are the settings in the common.yml file but nothing was being sent to port 25.

I installed postfix and that didn't work.  Then I removed postfix and installed sendmail and that didn't work.  I even tried editing the default sender name to something other than superdesk@localhost to see if my incoming email was blocked.  I am at a total loss and don't know what to do.  Please help!

Thanks@

Recommended Usage/Network Map

$
0
0

I think what I'm missing most from the documentation is something that the team must have drawn up before they ever started work on developing this project: a network map of how they expect this software to be installed and/or run, and what rough lines of communication they expect to occur between each server and each piece of software.

I realize that the team wants to be as neutral as possible so that each news outlet can use the setup that works best for them, but there are some standards that exist, and there had to be an idea of what would or wouldn't be supported before Superdesk ever left the whiteboard.

A VERY simple network map of how things are expected to be run (perhaps 2-3 network maps, if numerous options exist) would be extremely helpful to users who are considering Superdesk. A simple drawing could answer most overview questions. (Questions I currently can't find a simple answer to anywhere.)

Questions such as:

What is the expected network layout for Superdesk use? I think it's clear that one (and only one) Superdesk Server is needed to be the boss of everything for an organization. And the server uses mongodb, so it's probably safe to assume that the database should be running on the same server, and should not be on a separate machine. Right off the bat, we just said no Amazon ElasticBeanstalk and RDS (which doesn't support mongodb). No problem. Internally managed and hosted servers are available options still, as is an Amazon EC2 instance (in theory, not that I can get it to work). Amazon Lightsail is also a potential for this server still (although, again, I haven't found a way to get Superdesk to install even on a clear Ubunutu installation on a Lightsail virtual machine). Then, assuming you have Superdesk Server up and running somewhere that is both secure and stable, each user of Superdesk (editors, reporters, admins, etc) can each have their own machines with Superdesk Client running on them. (Or is Superdesk Client expected to only run on one machine, the same server that's running Superdesk Server? I honestly can't tell. See what I mean about needed a simple network map?) If I'm right about multiple  Superdesk Clients, then the network decisions now include whether to allow external-to-the-company access to Superdesk Server by the Superdesk Clients, or whether access is limited to only those inside the corporate network (whether physically inside or anywhere in the world via VPN). Those are normal network security decisions, not a big deal. At this point a simple list of all ports on the Superdesk Server that need to be accessible from non-localhost would be valuable, as security is the #1 concern, before even "is it useful?".

Now we're to the big one: the web server. There appears to be an attempt to be web server software-neutral, and to let people use their own web software, with Superdesk just managing the content and delivery internally. It would be nice if there was a list of recommended web server software (such as Newscoop, which sadly is no longer supported), but I understand that many companies may prefer to build this in-house. Superdesk advertises that it's API-driven, so one could theoretically store no data on the web server, and have it request everything from Superdesk Server every time it attempts to display a web page. Now, that's fine in theory, but obviously that's not actually a viable option, since the way Superdesk Server appears to have been designed, there's one and only one Superdesk Server, and it won't handle the load if a ton of API requests come in at once. Load balancers are a must on today's Internet, as is the ability to have more than one load-balanced server handling requests. There's no way this development team completely ignored reality and created a news CMS that can't handle having an article link make it to the front page of reddit, so they must have planned for load balancers and multiple instances of the web server. I just can't figure out where.

I assume that means a web server must be built by each news organization that can both display AND store data (e.g. articles and media), and that all data will be pushed to it by the Superdesk Server. Most of us don't want to pay for all the tech people required to manage that many servers and that much software, and so the popular thing today when creating a reliable web server (that can handle occasional big-hits when a story goes viral, and won't crash just because there's a link to them from reddit) is to have the web server running on an Amazon EC2 or ElasticBeanstalk instance that can automatically grow as needed, with load balancers in multiple physical locations, have the data stored in an Amazon RDS (database) instance, and have any non-database media (e.g. any videos and photos not stored in the database) stored in an Amazon S3 instance. You can't store ANY data and the web server software on the same machine, since then multiple instances would mean data would get un-synced and all your processes would quickly break down.

Is that what you guys have envisioned? I'm a bit worried that it's not, since Superdesk Web Publisher appears to have been built to work with exactly the type of network map I described earlier, one that won't support a lot of traffic, one where the web server doesn't store the data and just queries everything from a single solitary instance of Superdesk Server. If users need to create their own web server software that will store any/all data pushed from Superdesk Server, don't they also need a list of all fields that might exist, so their database is prepared for all eventualities? Is this data list somewhere easy to find, along with a list of all externally-accessible ports that are required for Superdesk Server? Am I completely misunderstanding how you expect this to be installed? (Again, a simple network map or two would solve such basic high-level questions for me and all other potential users.) One cannot be expected to install this software without such a high-level, very basic overview of what the network and software interactions should look like. Any help you guys can provide to me (and to anyone else who is trying to wrap their head around this) would be greatly appreciated. Remember, high-level and simple, there's no need to go into depth. (But if, somehow, the drawing on the whiteboard doesn't include a place for load balancers, then I'm pretty sure you've made a fundamental error, and your software can never be used by any 'real' organization, which would be really sad.) I'm sure you guys thought of this stuff before you spent the months required to write all this code, I just can't see the 'big picture' that you're envisioning, and I can't find a simple overview of it anywhere.

Thanks!

*edit - formatting

*edit2 - If I was completely off base about all this, and you really did design Superdesk Server as a standalone server made to handle the load of multiple web hosts making non-stop API requests, what sort of load did you test for, on what type of network? How many requests per second before things start to bog down?

Thanks!

Mongo Auth and Superdesk Server Initialization

$
0
0
If mongodb is set up to use authorization, I cannot initialize the superdesk server data.

Steps to replicate:

1. Setup mongodb to use auth. Restart mongodb.

2. Connect to mongo, use admin database, create user with root permissions (obviously lower is preferred, but for this test "root" still causes the error, and when testing it's easiest to use the highest level of auth to ensure it's not mongo roles that's causing the problem)

use admin
db.createUser(
   {
      user:  "superdeskadmin",
      pwd:   "MyPass12345",
      roles: 
         [
            "root"
         ]
   }
)

3. cd $path/server

4. vi settings.py, then add the following lines to the end of the file:



MONGO_DBNAME = env('MONGO_DBNAME','superdesk')

MONGO_URI = env('MONGO_URI','mongodb://superdeskadmin:MyPass12345@localhost/superdesk?authSource=admin')

LEGAL_ARCHIVE_DBNAME = env('LEGAL_ARCHIVE_DBNAME','legal_archive')

LEGAL_ARCHIVE_URI = env('LEGAL_ARCHIVE_URI','mongodb://superdeskadmin:MyPass12345@localhost/legal_archive?authSource=admin')

ARCHIVED_DBNAME = env('ARCHIVED_DBNAME','archived')

ARCHIVED_URI = env('ARCHIVED_URI','mongodb://superdeskadmin:MyPass12345@localhost/archived?authSource=admin')


5. sudo python3 manage.py app:initialize_data

No matter what I do, I get this error:



pymongo.errors.OperationFailure: not authorized on contentapi to execute command { createIndexes: "api_audit", indexes: [ { key: { subscriber: 1 }, name: "subscriber", background: true } ] }

6. On the exact same server, turn off auth for mongodb, restart mongo. Everything works fine.


Is this just me and something tweaky in my setup (currently Amazon Lightsail's pre-installed Bitnami Mean)? Has anyone else gotten mongodb and superdesk server initialization working with auth turned on in mongo?

*edit - missing parenthesis added

Problem installing on fresh ubuntu 16.04

$
0
0
I was trying to install Superdesk on Ubuntu 16.04 through the script found in https://raw.githubusercontent.com/superdesk/fireq/master/files/superdesk/install  
and I have not had good results. Redis, mongodb, elasticsearch node and npm are installed well as well as the processes of Build and Virtualenv (so they are marked inside the script) but at the time of installing the source code an error prevented me to continue:

When you try to install the requirements when websockets 3.3 arrives it gives an error like this:

downloading websockets-3.2.tar.gz
complete oupput from command python setup.py egg_info:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/tmp/pip-build-CimV2v/websockets/setup.py", line 19, in <module>
with open(os.path.join(root, 'README'), encoding='utf-8') as f:
TyperError: 'encoding' is an invalid keyword argument for this function

------------------------------------------------
Command "python setup.py egg_info2 failed with error code 1 in /tmp/pip-build-CimV2v/websockets



Any help?
Thanks!!!

install on windows

$
0
0
I'm newbie in pyton (and java, redis, mongo etc. world. Trying just install superdesk to play with him and can't install. Something wrong or missed in install instruction. OR in install scripts.

windows server 2016 (clean) x64 4Gb ram

installed recommended or new:
python 3.6.2x64
Git-2.14.1-64-bit.exe
node-v6.11.3-x64.msi
jre-8u144-windows-x64.exe 
elasticsearch-2.4.6.zip
mongodb-win32-x86_64-2008plus-ssl-3.4.7-signed.msi
Redis-x64-3.2.100.msi 

got last superdesk (master branch)

set environment TEMP and TMP to new C:\TEMP directory

I've got errors:
C:\superdesk\server>pip install -r requirements.txt
Collecting gunicorn==19.7.1 (from -r requirements.txt (line 1))
  Using cached gunicorn-19.7.1-py2.py3-none-any.whl
Collecting honcho==1.0.1 (from -r requirements.txt (line 2))
  Using cached honcho-1.0.1-py2.py3-none-any.whl
Collecting newrelic<2.67,>=2.66 (from -r requirements.txt (line 3))
  Using cached newrelic-2.66.0.49.tar.gz
Collecting Superdesk-Core from git+git://github.com/superdesk/superdesk-core.git@3e4f3fce1#egg=Super
desk-Core (from -r requirements.txt (line 5))
  Cloning git://github.com/superdesk/superdesk-core.git (to 3e4f3fce1) to c:\temp\10\pip-build-z0ora
yog\superdesk-core
error: unable to create file tests/io/fixtures/tag:reuters.com,0000:newsml_ISS149709:1618095828: Inv
alid argument
error: unable to create file tests/io/fixtures/tag:reuters.com,0000:newsml_L4N1FL0N0:1132689232: Inv
alid argument
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry the checkout with 'git checkout -f HEAD'

Command "git clone -q git://github.com/superdesk/superdesk-core.git c:\temp\10\pip-build-z0orayog\Su
perdesk-Core" failed with error code 128 in None

_________________________

C:\superdesk\server>python manage.py app:initialize_data
Traceback (most recent call last):
  File "manage.py", line 14, in <module>
    import superdesk
ModuleNotFoundError: No module named 'superdesk'

Superdesk API

Superdesk API

RSS Ingest not working

$
0
0
I have an rss feed that has been verified good from a known good source but Superdesk won't parse it.  I can't figure out how to get it to find any items in it.  Please advise.

Install Liveblog on hosting

$
0
0
Hello,

Can I install Live Blog on an hosting? I'm not the owner of the hosting server. I have bought an hosting package by an company. Can I install Live Blog then on my web server? 

Julian

liveblog live leads to 404

$
0
0
Hello. I am new to this and I tried to install it thru automatic installer in an ubuntu 16.04 vps.
backend is working, but when i am trying to see my liveblog timeline as "live" (embed) all I get is a 404 error.
Any help?

Webpack:build error on fresh Ubuntu 16.04

$
0
0
I've been trying to install superdesk using the latest version of the script @ https://github.com/superdesk/fireq/blob/files/superdesk/install .

Everything runs fine until webpack:build, where I get the following errors:

ERROR in ./~/superdesk-core/scripts/index.js
Module not found: Error: Cannot resolve module 'superdesk-ui-framework/dist/superdesk-ui-framework.min.css' in /opt/superdesk/client/node_modules/superdesk-core/scripts
 @ ./~/superdesk-core/scripts/index.js 5:0-69

ERROR in ./~/superdesk-core/scripts/vendor.js
Module not found: Error: Cannot resolve module 'superdesk-ui-framework/dist/superdesk-ui-framework' in /opt/superdesk/client/node_modules/superdesk-core/scripts
 @ ./~/superdesk-core/scripts/vendor.js 45:0-61
Warning: Task "webpack:build" failed. Use --force to continue.


The files that its looking for don't even seem to exist, so maybe a step is actually failing before? The only other warning I can find in the output is:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN client No description
npm WARN client No repository field.
npm WARN client No license field.


Anyone has solved this before? I tried installing it on Debian 9 before and it failed with the same error (actually, the script failed a few times before but everything else was fixable).

How to build source code

$
0
0
Hello ,

I am tryig to build superdesk source code in eclips . But i can not run it from eclips IDE . Is there any way ??


Regards
Elahee

server specs for a Superdesk installation

$
0
0
Dear list, 

I'm evaluating Superdesk for the following installation: 150 users maximum working at any time, 3,000 unique text news items daily, video files associated with most items. 

I'd like to keep things simple, so start with 1 server (at least 8cpu, 16G memory) to serve all Superdesk services and another one as a backup for mongodb. 

Do you think this is a sane setup? Or should I explore scaling on different levels? What could go wrong with the above scenario and how could I prevent it? 

Thanks a lot for any reply, 
Markos

Ingesting Newscoop articles into Superdesk

$
0
0
Hi, the RSS-ingest option in Superdesk shows several, different options for different RSS standards/providers, and I'm wondering if any of the options listed will work for importing articles into Superdesk from Newscoop (4.4) as I can't find mention of what RSS standard Newscoop outputs?

Alternatively, is it possible to transfer articles using the Newscoop API (I don't see RESTful API mentioned as an API option in Superdesk).

Thank you in advance for any anwers.

Said

Docker Install

$
0
0
Am I, the only one have trouble to install superdesk on docker using the docker hub link says error 404

If I choose the method to install Superdesk Manually on docker do I have to get all dependencies manually installed?
Viewing all 288 articles
Browse latest View live